PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
|
Contents
Index
|
23.8.1 Prior confirmation
First, confirm the states of the current primary MDS and the secondary MDS by using the sfcrsinfo(1M) command.
# sfcrscinfo -m /dev/sfdsk/gfs/rdsk/volume1
/dev/sfdsk/gfs/dsk/volume1:
FSID MDS/AC STATE S-STATE RID-1 RID-2 RID-N hostname
1 MDS(P) wait - 0 0 0 host1
1 AC run - 0 0 0 host1
1 MDS(S) run - 0 0 0 host2
1 AC run - 0 0 0 host2
1 MDS(I) imag - 0 0 0 host3
1 AC run - 0 0 0 host3
1 MDS(I) imag - 0 0 0 host4
1 AC run - 0 0 0 host4
|
First, confirm the following:
- The file system must be mounted on the node of the primary server.
You can confirm this by checking that STATE and S-STATE of the Access Client (AC) on host1, that is a hostname of MDS(P), are "run" and "-", respectively.
- The file system must be mounted on the node on the secondary server.
You can confirm this by checking that STATE and S-STATE of the Access Client (AC) on host2, that is a hostname of MDS(S), are "run" and "-", respectively.
- The node of the primary MDS and its state is "run" and "-".
The primary MDS is running normally on host2 for which STATE and S-STATE are "run" and "-" in the above example.
Note that, since the primary server is equivalent to host1 that is displayed as MDS(P), the primary MDS is running on a node other than the defined host.
- The node of the secondary MDS and its state is "wait" and "-".
The secondary MDS is running normally on host1 for which STATE and S-STATE are "wait" and "-" in the above example.
Note that, since the secondary server is equivalent to host2 that is displayed as MDS(S), the secondary MDS is running on a node other than the defined host.
For details on sfcrscinfo(1M), see "F.2.26 sfcrscinfo(1M)."
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004