vxfs mount: mount option(s) incompatible with file system

[Olga_1]

On system reboot /home is not mounted automatically. Later when the system is up I am able to mount /home:
mount /dev/vg06/lv_u17 /home

Here is the error from /etc/rc.log:
mountall: cannot mount /dev/vg06/lv_u17
mountall: diagnostics from mount
vxfs mount: mount option(s) incompatible with file system /dev/vg06/lv_u17
checking quotas

Any comments are appreciated.

[Stefan Farrelly]

looks like your entry in /etc/fstab is wrong. It should look something like;

/dev/vg06/lv_u17 /home vxfs delaylog 0 2

[Olga_1]

Thank you for your answer.

/etc/fstab:

/dev/vg06/lv_u17 /home vxfs rw,suid,largefiles,delaylog,datainlog 0 2

looks like any other entry.

[Sajid_1]

hi,

Once the system booted, check this command:
# mount -a
This will read the entries in the /etc/fstab file and then you will know that if there is some problem with the entries. It should be normally like this:
/dev/vg00/lvol4 /home vxfs delaylog 0 2

hth

[Sajid_1]

hi again,

Did you get some error from this command ?
# mount -a

Once the filesystem is mounted manually, you can also compare the entries of fstab with /etc/mnttab. You can replace the fstab entry with mnttab entry if there is some error.

[Olga_1]

this is what I got:

mount -a
mount: /dev/vg06/lv_u17 is already mounted on /home
plus the rest of the already mounted FS.

[Sajid_1]

hi,

Actually I meant, to run that command when the filesystem was not mounted. In your case just after system started without the /home. By doing this you will identify if any error in /etc/fstab file. Now just umount the /home manually and try running again:
# cd
# umount /home
# mount -a

[Christopher McCray_1 · Accepted solution]

Hello,

Check out this doc:

http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000058669496

I think this will help you.

Chris

[Olga_1]

Unfortunately, I cannot unmount /home now, as useres aer logged in to the system. I will be able to do it on weekend.
Thank you for your help.

[Sanjay_6]

Hi Olga,

Suggest you unmount the home filesystem and run fsadm aginst this filesystem raw lv. you may find the filesystem may have been created with nolargefiles option, while it is trying to mount the filesystem with largefiles option. If it is so, Again use fsadm to change the nolargefiles to larefiles.

Hope this helps.

Regds

[Stefan Farrelly]

I think the system is expecting /home to be in vg00. It activates vg00 first, mounts its lvols - and your /home isnt in vg00 so doesnt mount, then it activates the other vg's (yours is in vg06) later.

If you cant have /home in vg00 because of size restrictions then I think you should create /home in vg00 but a very small size, and then create a subdir under it called something like users which is a mountpoint for /dev/vg05/lv_u17 (where all your large user accounts can live). This should work fine.

[Sajid_1]

hi,

I don't think that the problem is with /dev/vg00 expectation. The normal practise is to keep the /home under vg00 as Stefan said, but even if you create /home under any other VG it should not bother the system. I do have some systems which was configured like this (/home in /dev/vg03) and I never had any issues like this.

The problem should be with the largefile settings, you can confirm it on the next reboot (mount -a).

gl,