VxVM Volume based file systems fail to mount during boot time on SLES10 systems


VxVM Volume based file systems fail to mount during boot time on SLES10 systems


 This issue occurs because the file system attempts to check and mount the VxVM device before the device is present.


On SLES10 systems, the system may fail to boot when a file system is mounted on a Veritas Volume Manager (VxVM) device. File system fsck and mount fails because VxVM devices are not present at system boot time and the fsck is initiated before the Volumes are available to the system. 


This issue is due to how the Operating System's init scripts are designed.  Expectation is that network based file systems should not be mounted until later in the startup process pending additional service startups.

SUSE 10 init scripts do not exclude _netdev devices from initial mount operation as expected, addition of the "hotplug" mount option is necessary to postpone attempts to mount VxVM based volume file systems until Volume Manager can startup.
Manual Page of mount command:
 _netdev  - The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).
hotplug - 

Edit the file system entry in /etc/fstab file to include the file system options _netdev and hotplug.


/dev/vx/dsk/vg/lvol0 /mnt vxfs _netdev,hotplug 1 2

For a permanent solution it would be recommended to contact Novell to get the permanent fix in SuSE:

To add _netdev in boot.localfs

# fsck $FSCK_PROGRESSBAR -R -A -m -a $FSCK_FORCE -t noopts=hotplug

Should be

# fsck $FSCK_PROGRESSBAR -R -A -m -a $FSCK_FORCE -t noopts=hotplug,_netdev



Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)