VxFS mount options ignored for ROOT FS

[Ralph Grothe]

Hi,

just out of curiosity,
while I was revisiting the mount options for VxFS in the VxFS doc (because I have an Oracle DB's cooked I/O performance impedance on another mount point) I was wondering why the rootfs was mounted with the "log" option (i.e. the default) while in fstab it is asked to be mounted with the "dalylog" option.

I know that the latter is less crash proof
(simply because the writing to the intent log is delayed in favour of sooner return to pending processes).
Maybe it isn't even possible to have rootfs mounted as delaylogged because of the prominence of this filesystem?
But the delalog option is as far as I remember a remnant from the installation.

# mount -p|head -1
/dev/vg00/lvol3 / vxfs log 0 1

# grep vg00/lvol3 /etc/fstab
/dev/vg00/lvol3 / vxfs delaylog 0 1

[James R. Ferguson · Accepted solution]

Hi Ralph:

I must confess that I never noticed this. Technical Knowledge Base document #UFSKBRC00012145 explains this. In part, it notes that the 'log' option is the default used by the kernel during bootup and that there is no reason for alarm. Change your 'etc/fstab' to match if it pleases you.

Regards!

...JRF...

[Arunvijai_4]

Hi Ralph,

Release notes of VxFS 3.5 and 4.1 says, it is the default option.

http://docs.hp.com/en/5991-2710/ch06s05.html

The delaylog option is now the default intent logging mount option. The change of the default mount option from log to delaylog does not increase the risk of data loss, but allows Base-VXFS to cache data to improve performance.

Not sure why this is happening,

-Arun