Changing Share Options on an NFS File System

If you use the rw, rw=, ro, or ro= options to the share -o command, NFS fault monitoring will work best if you grant access to all the physical host names or netgroups associated with all Sun Cluster servers.

If you use netgroups in the share(1M) command, add all of the Sun Cluster host names to the appropriate netgroup. Ideally, you should grant both read and write access to all the Sun Cluster host names to enable the NFS fault probes to do a complete job.

Before you change share options, read the share_nfs(1M) man page to understand which combinations of options are legal. When modifying the share options, execute your proposed new share(1M) command, interactively, as root, on the Sun Cluster server that currently masters the logical host. This will give you immediate feedback as to whether your combination of share options is legal. If the new share(1M) command fails, immediately execute another share(1M) command with the old options. After you have a new working share(1M) command, change the dfstab.logicalhostname file to incorporate the new share(1M) command.

How to Change Share Options on an NFS File System

1. From a cconsole(1) window, use an editor such as vi to make the appropriate changes to the dfstab.logicalhost files.

   By using a cconsole(1) window, you can make changes on all the 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.

   If a reconfiguration is not possible, you can run the share(1M) command with the new options. Some changes can cause the fault monitoring subsystem to issue messages. For instance, a change from read-write to read-only will generate messages.