The vxfs file system module automatically loads on the first reference to a VxFS file system; this occurs when a user tries to mount a VxFS file system.

In some instances, you may find it efficient to load the file system module manually. For example, some larger class systems can have many dual interface I/O cards with multiple disk chains attached. The device interrogation process when such a system is rebooted can be very time consuming, so to avoid doing a reboot, use the modprobe command to load the vxfs module:

# modprobe vxfs ; modprobe vxportal ; modprobe fdd

Do not use the insmod command to load the vxfs module as insmod does not examine the module configuration file /etc/modprobe.conf.

To determine if the modules successfully loaded, use the lsmod command as shown here:

# lsmod | grep vxportal
vxportal              2952           0
vxfs                  3427960        0    fdd vxportal
# lsmod | grep fdd
fdd                   67212          0    (unused)
vxfs                  3427960        0    [fdd vxportal]
# lsmod | grep vxfs
vxfs                  3427960        0    [fdd vxportal]

The first field in the output is the module name. You can unload the modules by entering:

# rmmod fdd
# rmmod vxportal
# rmmod vxfs

The rmmod command fails if there are any mounted VxFS file systems. To determine if any VxFS file systems are mounted, enter:

# df -T | grep vxfs