PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.2 (Linux)

A.2.29 File System Auto Mount

File systems created on volumes in classes other than the root class (local classes and shared classes) cannot be mounted with the OS auto mount feature at OS startup.

This is because the OS auto mount process is executed before the GDS startup script "/etc/*.d/*sfdsk*" is executed.

When including file systems created on volumes in classes other than the root class in the /etc/fstab file, be sure to describe the "noauto" option in the forth field. In the File System Configuration screen of GDS Management View, select "no" to "mount." If "yes" to "mount" is selected, the noauto option is not declared.

If the noauto option is not declared, the following message is displayed at OS startup and mounting fails.

mount: special device /dev/sfdsk/Class Name/dsk/Volume Name does not exist

Additionally, if the noauto option is not declared and if a specification to check file systems at OS startup is made in the sixth field, the following message is displayed and the OS does not start.

fsck.ext3: No such file or directory /dev/sfdsk/Class Name/dsk/Volume Name:

For Shared Classes
To mount or unmount file systems on volumes in shared classes when starting or exiting cluster applications, /etc/fstab file setting and Fsystem resource setting are necessary. When using GFS, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide." For details, see "PRIMECLUSTER Global File Services Configuration and Administration Guide."

For Local Classes [Linux2.6]
To automatically mount file systems created on volumes in local classes at OS startup, use a startup scrip such as /etc/rc.local that is executed after the GDS startup script "/etc/*.d/*sfdsk*" for mounting.