Editing mcf Files for a Clustered File System

The lines that define a particular file system must be identical in the mcf files on all host systems that support the file system. Only one mcf file can reside on a host. Because you can have other, additional file systems defined in an mcf file, the mcf files on different hosts might not be identical.

How to Edit mcf Files for a Clustered File System

Perform this procedure for each host that you want to include in a shared file system in an Oracle Solaris Cluster environment.

1. Log in to the host.
2. Become superuser.
3. Ensure that an mcf file on this node contains lines that define the new file system copied from the primary node's mcf file.

   • If an mcf file does not exist on this node, create one and include the file system lines.

   • If an mcf file already exists on this node, add the lines for the new file system.

4. Copy the lines that define the file system from the primary node's mcf file to this node's mcf file.
5. Use the samfsconfig command to locate the local device names for each additional host to be configured in the shared file system.

   The samfsconfig command generates configuration information that can help you to identify the devices included in the shared file system. Issue a separate samfsconfig command on each client host. Note that the controller number might not be the same controller number as on the metadata server because the controller numbers are assigned by each client host.

6. Update the mcf file on other client hosts.

   Use vi or another editor to edit the mcf file on one of the client host systems. The mcf file must be updated on all client hosts to be included in the shared file system. The file system and disk declaration information must have the same data for the Family Set name, Equipment Number, and Equipment Type fields as the configuration on the metadata server. The mcf files on the client hosts must also include the shared keyword. The device names, however, can change as controller assignments can change from host to host.

   To access or mount a shared file system, a host system must have that file system defined in its mcf file. The content of the mcf files varies depending on the type of Oracle Solaris Cluster hosts:

   • The primary metadata server

   • Potential metadata servers

     All hosts can be metadata servers because the Oracle Solaris Cluster software fails over system resources in the event of a node failure.

     ---

     Note - Clients within the cluster are supported within the SC-RAC configuration only. Other configurations have clients within the cluster that serve as passive metadata servers only. They exist as potential metadata servers for failover capabilities but are not supported for reading or writing data as a shared Sun QFS client.

     ---

Example 4-1 mcf File Using Hardware RAID and Oracle Solaris Cluster

The following sample mcf file includes six shared file systems.

psfb1% more /etc/opt/SUNWsamfs/mcf
OraHomes 20 ma OraHomes - shared
/dev/did/dsk/d1s0 21 mm OraHomes -
/dev/did/dsk/d2s0 22 mr OraHomes -
/dev/did/dsk/d3s0 23 mr OraHomes -

CrsHomes 30 ma CrsHomes - shared
/dev/did/dsk/d6s0 31 mm CrsHomes -
/dev/did/dsk/d7s0 32 mr CrsHomes -

OraData 40 ma OraData - shared
/dev/did/dsk/d8s0 41 mm OraData -
/dev/did/dsk/d9s0 42 mr OraData -
/dev/did/dsk/d10s0 43 mr OraData -
/dev/did/dsk/d11s0 44 mr OraData -

votingdisk1 50 ms votingdisk1 - shared
/dev/did/dsk/d4s1 51 md votingdisk1 -
votingdisk2 60 ms votingdisk2 - shared
/dev/did/dsk/d4s2 61 md votingdisk2 -
votingdisk3 70 ms votingdisk3 - shared
/dev/did/dsk/d4s3 71 md votingdisk3 -