PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
Contents Index PreviousNext

Part 2 Global File Services Local File System> Chapter 10 Using GFS Local File System in RMS cluster Operation

10.7 Using GFS Local File System as NFS Server in Stand-by Operation

The following conditions must be satisfied to use the GFS Local File System as an alternate cluster file system and the NFS server in stand-by operation:

  1. The device numbers of all partitions composing the GFS Local File System must match in both nodes used for stand-by operation.
  2. The specification for forcibly loading the GFS Local File System module must be able to be registered in /etc/system for both nodes.
  3. The GFS Local File System module forcibly loaded on both nodes must have the same slot number.

First, execute the ls command to confirm that the device major and minor numbers on each node match. If the numbers do not match, check the cluster environment again.

Next, as explained in the previous section, setup the GFS Local File System for use as an alternate cluster file system. Then, execute the vi command to add the following statement to the /etc/system file at the position where "forceload" is specified.

forceload: fs/sfxfs

After adding the above statement to the files on both nodes, reboot the system.

Finally, execute the following command to confirm that the slot number of kernel module sfxfs of GFS Local File System is the same on both nodes. If the numbers do not match, check the forceload statement on both nodes.

# crash <<!
vfssw
!

The above command leads to an output of the following list:

dumpfile = /dev/mem, namelist = /dev/ksyms, outfile = stdout
> FILE SYSTEM SWITCH TABLE SIZE = XX
SLOT NAME FLAGS
1 specfs 0
2 ufs 0
3 fifofs 0
4 namefs 0
5 proc 0
6 s5fs 0
7 nfs 0
8 sfxfs 0
....

In the above example, the slot number is 8.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004