Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

mount pt issue

Status
Not open for further replies.
AIXFinder

AIXFinder

IS-IT--Management
Jan 4, 2007
97
US
root:/> oslevel -r
5100-04

root:/> mount backup1
mount: 0506-334 backup1 is not a known file system.

root:/> cd backup1

root:/backup1>

root:/> df -k |grep back
root:/>

root:/backup1> touch abc

root:/backup1> ls -al
total 8
drwxrwsrwx 2 d_stp d_stp 256 Jan 19 10:10 .
drwxr-xr-x 36 root system 4096 Jan 18 23:00 ..
-rw-r--r-- 1 root d_stp 0 Jan 19 10:10 abc

backup1 is not mounted, but I can cd to it, and can write files.

How do you fix this issue? I need to see /backup1 as a mount pt.

thx
 
Sort by date Sort by votes
You have a directory called /backup1 but, if it is not defined within /etc/filesystems, then the mount command does not know what to mount over it.

If it's an internal file system this should have been sorted out when the FS was created. If it's an NFS file system then the mount command should have been
Code: 
mount remote_server:/exported_system /backup1

Ceci n'est pas une signature
Columb Healy
 
Upvote 0 Downvote
ok. I am geeting this..

root:/> mount /backup1
mount: 0506-324 Cannot mount /dev/backuplv on /backup1: There is a request to a device or address that does not exist.
root:/> mount backup1
mount: 0506-334 backup1 is not a known file system.

in etc/filesystems

/backup1:
dev = /dev/backuplv
vfs = jfs
log = /dev/loglv01
mount = true
check = false
options = rw
account = false

root:/> mount -t jfs /dev/backuplv /backup1
mount: 0506-310 'Directory/File Name' is not valid with the -t flag..

Can you please help?

thx
 
Upvote 0 Downvote
root:/> mount -v jfs /dev/backuplv /backup1
mount: 0506-324 Cannot mount /dev/backuplv on /backup1: There is a request to a device or address that does not exist.

root:/> ls -al /dev/backuplv
brw-rw---- 1 root system 57, 1 Dec 03 23:03 /dev/backuplv

/dev/backuplv exists..., but can't mount still.
 
Upvote 0 Downvote
Based on your output above, it does indeed look like the backup1 file system is defined in /etc/filesystems. However, since you are still getting the "mount: 0506-324 Cannot mount" error, it looks like the underlying device is no longer present.


According to this:

/backup1:
dev = /dev/backuplv
vfs = jfs
log = /dev/loglv01
mount = true
check = false
options = rw
account = false

you should have the block file: backuplv in your /dev directory. Type this:

ls -la /dev/backuplv

You should get output similar to this:

brw-rw---- 1 root system 45, 3 Jul 08 2006 /dev/backuplv

If not, you (or someone) will either need to update /etc/filesystems to remove that entry since it no longer exits OR take the appropriate steps to recover/recreate the necessary files for that mount point.
 
Upvote 0 Downvote
Try these commands

lslv backuplv
errpt

I'm thinking along the lines of a missing/faulty disk :-(


HTH,

p5wizard
 
Upvote 0 Downvote
AIXFinder - I see you beat me to what I was suggesting.

Hmm..... do you know what volume group the mount point is supposed to be in? If so, perhaps you can do this:

lsvg -l <volume group name>

and see if /backup1 is listed in it.
 
Upvote 0 Downvote
LOGICAL VOLUME: backuplv VOLUME GROUP: backupvg
LV IDENTIFIER: 0003403a00004c00000000fc05bbdc03.1 PERMISSION: ?
VG STATE: inactive LV STATE: ?
TYPE: jfs WRITE VERIFY: ?
MAX LPs: ? PP SIZE: ?
COPIES: ? SCHED POLICY: ?
LPs: ? PPs: ?
STALE PPs: ? BB POLICY: ?
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: /backup1 LABEL: /backup1
MIRROR WRITE CONSISTENCY: ?
EACH LP COPY ON A SEPARATE PV ?: yes



root:/> lsvg -l backupvg
0516-010 : Volume group must be varied on; use varyonvg command.
root:/> varyonvg backupvg
PV Status: hdisk72 000382aa77d5d824 PVACTIVE
hdisk73 000382aa77d5d964 PVACTIVE
hdisk57 000382bab07b421b PVACTIVE
hdisk56 000382bab07b4154 PVACTIVE
hdisk55 000382bab07b4086 PVACTIVE
hdisk54 000382bab07b3fbe PVACTIVE
hdisk87 000382aaa4568ef8 PVACTIVE
hdisk88 000382aaa4570bce PVACTIVE
hdisk89 000382aaa4572028 PVACTIVE
hdisk90 000382aaa45734bf PVACTIVE
hdisk91 000382aaa4574d67 PVACTIVE
hdisk92 000382aaa4576491 PVACTIVE
hdisk93 000382aaa4578061 PVACTIVE
hdisk94 000382aaa4579b32 PVACTIVE
hdisk95 000382aaa457ba85 PVACTIVE
hdisk96 000382aaa457d91c PVACTIVE
hdisk97 000382aaa457fbaf PVACTIVE
hdisk98 000382aaa4581d98 PVACTIVE
hdisk99 000382aaa45843f4 PVACTIVE
hdisk100 000382aaa458697d PVACTIVE
0516-1341 varyonvg Please reboot with the 64bit kernel and try again.

ok....
I changed 64 bit to 32 bit. Is that the reason???
All of the other files show up monut pt though....
 
Upvote 0 Downvote
if it is an enhanced concurrent VG you would need 64 bit kernel I believe

HTH,

p5wizard
 
Upvote 0 Downvote
I looked at this error again.

root:/> lsvg -l backupvg
0516-010 : Volume group must be varied on; use varyonvg command.
root:/> varyonvg backupvg
PV Status: hdisk72 000382aa77d5d824 PVACTIVE
hdisk73 000382aa77d5d964 PVACTIVE
hdisk57 000382bab07b421b PVACTIVE
hdisk56 000382bab07b4154 PVACTIVE
hdisk55 000382bab07b4086 PVACTIVE
hdisk54 000382bab07b3fbe PVACTIVE
hdisk87 000382aaa4568ef8 PVACTIVE
hdisk88 000382aaa4570bce PVACTIVE
hdisk89 000382aaa4572028 PVACTIVE
hdisk90 000382aaa45734bf PVACTIVE
hdisk91 000382aaa4574d67 PVACTIVE
hdisk92 000382aaa4576491 PVACTIVE
hdisk93 000382aaa4578061 PVACTIVE
hdisk94 000382aaa4579b32 PVACTIVE
hdisk95 000382aaa457ba85 PVACTIVE
hdisk96 000382aaa457d91c PVACTIVE
hdisk97 000382aaa457fbaf PVACTIVE
hdisk98 000382aaa4581d98 PVACTIVE
hdisk99 000382aaa45843f4 PVACTIVE
hdisk100 000382aaa458697d PVACTIVE
0516-1341 varyonvg Please reboot with the 64bit kernel and try again.


/backup1 filesystem might have some oracle backup files from 9i, which was on 64 bit.

Right now, it is on 32 bit.

Is that because this error (0516-1341 varyonvg Please reboot with the 64bit kernel and try again.) returns?

If my guess (/backup1 filesystem doesn’t like files from 64 bit) is right, how do you wipe out all files under /backup1, which is not mounted currently?
 
Upvote 0 Downvote
It is not about a filesystem, it is the VG which your system won't varyon in 32bit kernel. Probably on varyon, the system needs to load a kernel extension which is a 64bit KE and it cannot load into a 32 bit kernel.

Any particular reason why you went from 64bit ot 32bit?


HTH,

p5wizard
 
Upvote 0 Downvote
>> Any particular reason why you went from 64bit ot 32bit?

I am runing Oracle 8i.
 
Upvote 0 Downvote
You can get a fix from Oracle to get 8i to run on a 64bit AIX kernel.

The oracle post/wait kernel extension is for 32 bit AIX kernel, but there is a 64bit AIX kernel version of it also.


HTH,

p5wizard
 
Upvote 0 Downvote
It is MetaLink note 231901.1 you need to check out.


HTH,

p5wizard
 
Upvote 0 Downvote
I have two separate AIX nodes and need to nfs mount two filesystems:

- STM1 node is the one that needs to pull the data from RTP1 node.
- RTP1 node has /backup2pdc and /backup2pdctmp filesystems that have all of the data.

/backup2pdc and /backup2pdctmp filesystems are already nfs mounted with RTP2.

Please note that RTP1 and RTP2 are on dual nodes; SMIL1 (this is the node we are having issues with /backup1 as discussed above threads) is a separate node.

How do you nfs mount this?
If nfs mount possbile, it will resolve my immediate need..

Thanks.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

PravinKatkade
  • Locked
  • Question
AIX IP filtering issue
Replies
1
Views
172
unixfreak
unixfreak
WFdon
  • Locked
  • Question
NFS mount with non-identical UIDs
Replies
0
Views
128
WFdon
WFdon
Amandeep Gautam
  • Locked
  • Question
equivalent of /proc/mounts in AIX 1
Replies
5
Views
285
unixfreak
unixfreak
yuvarakasil
  • Locked
  • Question
IBM Pureflex network connectivity issue
Replies
0
Views
143
yuvarakasil
yuvarakasil
cpu533
  • Locked
  • Question
vios restore issue
Replies
1
Views
144
cpu533
cpu533

Part and Inventory Search

Sponsor

Back
Top