Adding an Existing File System to a Logical Host

After Sun Cluster is running, use the following procedures to add an additional file system to a logical host.

Use care when manually mounting multihost disk file systems that are not listed in the Sun Cluster vfstab.logicalhost and dfstab.logicalhost files. If you forget to unmount that file system, a subsequent switchover of the logical host containing that file system will fail because the device is busy. However, if that file system is listed in the appropriate Sun Cluster vfstab.logicalhost files, the software can forcefully unmount the file system, and the volume manager disk group release commands will succeed.

How to Add an Existing File System to a Logical Host

1. From a cconsole(1) window, use an editor such as vi to add an entry for the file system to the /etc/opt/SUNWcluster/conf/hanfs/vfstab.logicalhost file.

   By using a cconsole(1) window, you can make changes on all potential masters of these file systems.

2. Run the mount(1M) command to mount the new file system.

   Specify the device and mount point. Alternatively, you can wait until the next membership reconfiguration for the file system to be automatically mounted.

   Here is an example for Solstice DiskSuite.

   # mount -F ufs /dev/md/hahost1/dsk/d2 /hahost1/2

   Here is an example for VERITAS Volume Manager.

   # mount -F vxfs /dev/vx/dsk/dg1/vol1 /vol1

3. Add the Sun Cluster HA for NFS file system to the logical host.

   1. From a cconsole(1) window, use an editor such as vi to make the appropriate entry for each file system that will be shared by NFS to the vfstab.logicalhost and dfstab.logicalhost files.

      By using a cconsole(1) window, you can make changes on all potential masters of these file systems.

   2. Execute a membership reconfiguration of the servers.

      # haswitch -r

      Refer to the Sun Cluster 2.2 System Administration Guide for more information on forcing a cluster reconfiguration.

      Alternatively, the file system can be shared manually. If the procedure is performed manually, the fault monitoring processes will not be started either locally or remotely until the next membership reconfiguration is performed.