One file system not mounted after rebooting hp-ux 11i

[Simon Qu]

Every time when I rebooted our hp-ux system, all file systems are automatically mounted except the below one, I have an entry in fstab file like this:
/dev/vg03/lvol3 /testdb vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2

After rebooting, I have to manually mount it.

Does anybody know what is the problem?
Thanks in advance.

[RAC_1]

Do you get any error in /etc/rc.log?
Check rc log for errors.
Also after reboot when manually mounting it, how do you mount?

Try mounting it as mount /testdb.

[Jeff Schussele]

Hi Simon,

Do you run Service Guard?
If so you'll have to add this VG/LV/FS to the /etc/lvmrc file to the custom_vg_activation function if AUTO_VG_ACTIVATE=0

If no MC/SG then you must make sure the mount options in fstab match the actual option - run
fsadm /testdb

HTH,
Jeff

[Jeff Schussele]

Sorry - you just need the VG in the lvmrc file.
Entry would be like
/sbin/vgchange -a y /dev/vg03

Jeff

[A. Clay Stephenson]

Your fstab entry look okay. When you mount it manually, are you able to simply mount it as "mount /testdb"? If so, your fstab entry is perfect. Is an fsck required before you are able to mount? I assume that the volume group has been activated. Do you see anything in /etc/rc.log?

[Simon Qu]

There is no error in rc.log. I manually mount it like this:
mount /dev/vg03/lvol3 /testdb

[RAC_1]

Try mounting it as mount /testdb and post.

Also what is the output of this commanf mksf -F vxfs -m /dev/vg03/lvol3.

[Simon Qu]

Maybe, I did not state my question clearly.
After reboot, I mounted as
mount /dev/vg03/lvol3 /testdb
and it worked fine. My question is why it was not automatically mounted during the reboot.

[RAC_1]

There are many possibilities.

If you try mounting it as mount /testdb and it is OK, then you /etc/fstab file entry is OK.

Also as I said earlier post the resutl of mkfs -F vxfs -m /dev/vg03/lvol3.
Also post the result of mount /testdb

[A. Clay Stephenson]

Your mount /dev/vg03/lvol3 /testdb is not as good a test of fstab as simply "mount /testdb". Does that work? That method of mounting will use all the options specified in the fstab entry unlike your version of the manual mount command which is simply using the defaults. It is possible, for example, that you are using OnlineJFS options on a system that does not have OnlineJFS.


I have a feeling that the problem is before this entry in /etc/fstab. Please attach your entire fstab.

[RAC_1]

After you mount lvol as
mount /dev/vg03/lvol3 /testdb

Post the results of mount -p |grep "testdb"

That will give you what options are used for mounting that lvol.

[Simon Qu]

/ mount -p |grep "testdb"
/dev/vg03/lvol3 /testdb vxfs log,nodatainlog 0 0

mount /testdb
vxfs mount: mount option(s) incompatible with file system /dev/vg03/lvol3

fstab file:
/etc cat fstab
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /users vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvol9 /novell vxfs delaylog 0 2
/dev/vg00/lvol10 /home vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg01/lvol1 /db01 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg02/lvol1 /db02 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg02/lvol2 /avail2db vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg03/lvol1 /db03 vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg03/lvol3 /testdb vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2
/dev/vg03/lvol2 /oraclewgs vxfs delaylog 0 2

[Sridhar Bhaskarla]

Hi,

Take out "largefiles" from /etc/fstab corresponding to /testdb. If this filesystem is not enabled with largefiles, then it will give out an error.

Or enable largefiles on that logical volume. If you have online JFS, then

fsadm -o largefiles /testdb (when the filesystem is mounted).

If you don't have onlineJFS, then umount /testdb and run

fsadm -F vxfs -o largefiles /dev/vg03/lvol3

You don't need largefiles in /etc/fstab even if the filesystem supports largefiles.

-Sri

[RAC_1]

One thing is sure your mount options in /etc/fstab are conflicting with when you mount as mount /dev/vg03/lvol3 /testdb.

Post the reults of mkfs -F vxfs -m /dev/vg03/lvol3--This will tell you what options were used to create the file system. These options should go in /etc/fstab entry and nothing else.

I doubt largefiles option in fstab is causing problem. Also post the results of fstyp -v /dev/vg03/lvol4.

[Simon Qu]

/ mkfs -F vxfs -m /dev/vg03/lvol3
mkfs -F vxfs -o ninode=unlimited,bsize=4096,version=4,inosize=256,logsize=512,n0

/ fstyp -v /dev/vg03/lvol3
vxfs
version: 4
f_bsize: 8192
f_frsize: 4096
f_blocks: 5120000
f_bfree: 1091821
f_bavail: 1075018
f_files: 269136
f_ffree: 272944
f_favail: 272944
f_fsid: 1073938435
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 0
f_fsindex: 7
f_size: 5120000

[Sridhar Bhaskarla · Accepted solution]

The option that I could see conflict with the actual filesystem configuration most of the times is 'largefiles'. And your mkfs output confirmed it.

Either take out largefiles from /etc/fstab or enable largefiles on the system as I said before.

-Sri

[RAC_1]

The largefiles option in /etc/fstab is causing the problem. Take it out and mount it as mount /testdb, it will get mounted. In case you want to enable largefiles on the file system do as told by Shri.

[Simon Qu]

Thank all you guys, you resolved my problem.