VxFS filesystems fail to mount at boot on Linux systems.

book

Article ID: 100005035

calendar_today

Updated On:

Resolution

To resolve the failure to mount vxfs filesystems at boot, additional options may be specified in the /etc/fstab file.
These options allow the filesystems to mount later in the boot process.

An example of an entry for a vxfs filesystem:

/dev/vx/dsk/testdg/testvolume /mountpoint       vxfs    _netdev,hotplug            0 1

 

In the above configuration, the fifth field setting (mount at boot) is set to 0. The fsck command run at boot time will not be run against the filesystem.
Later in the boot process the VxVM startup scripts will run. The VxVM startup script initiates an additional scan of /etc/fstab.
At this point, a mount command is initiated to process any vxfs filesystem entries.

Changing of the options in /etc/fstab for the vxfs filesystems does require modification of the default setting (off) for "netfs".
To verify the current setting of "netfs", run the following command:

# chkconfig --list |grep netfs

If the output indicates "netfs" is off at all run-levels as below:

netfs           0:off   1:off   2:off   3:off   4:off   5:off   6:off

 

then it is necessary to enable "netfs".

If the output is as below:

netfs           0:off   1:off   2:off   3:on    4:on    5:on    6:off

 

then "netfs" is already enabled and the vxfs filesystems should successfully mount at boot.

To enable the "netfs" service functionality (if disabled), perform the following:


# chkconfig netfs on

This setting is persistent across reboots.

If it is desired to start the "netfs" process on the system that is currently up, issue the following command:

# service netfs start


 

 

Applies To

RHEL5

RHEL4

SLES9

SLES10

SLES11

Issue/Introduction

VxFS filesystems fail to mount at boot. Error Message