For the following cases, GDS cannot determine the disk containing the latest data. In this case, a user must select the copy source disk for the synchronization copying to take the restoration procedure.
Both nodes are stopped after the operation with an INVALID status slice, and the cluster application is forcibly started in the other node with the INVALID status slice.
Both nodes are stopped after the standby node was stopped, and the cluster application is forcibly started with the node that was on standby.
After the communication between the nodes is disabled due to the cluster interconnect failure, the operational node is panicked and switched.
In the above cases, starting the netmirror volume and the synchronization copying are inhibited.
The restoration procedure for the above a and b is as follows.
Restoration Procedure
Start the stopped node.
Stop RMS on both nodes.
Restore the iSCSI device.
Take this procedure on the node where the cluster application is forcibly started last time.
# /etc/opt/FJSVsdx/bin/sdxiscsi_ctl -F -e init |
The disk of the stopped node must be recognized on the operating node. For -d option of the sdxfix command, specify the disk of the stopped node.
Take this procedure on the operating node.
# sdxfix -D -c class_name -d disk_name -x Devlabel |
-x Devlabel is the option to specify the restoration of the device information. Use this option only for this restoration procedure.
If the copy source slice for the synchronization copying is in INVALID, restore the slice state. For -d option of the sdxfix command, specify the copy source disk for the synchronization copying.
Take this procedure on either of both nodes.
# sdxfix -V -c class_name -v volume_name -d disk_name -x NoRdchk |
-x NoRdchk is the option to skip the read check of the slice. Use this option only for this restoration procedure.
The node that the cluster application last started can be checked with the following procedure.
Execute the following command on both nodes and compare the results with both nodes.
# /etc/opt/FJSVsdx/bin/sdxiscsi_ctl -L -e time -c cluster_name |
[Execution example]
Node 1
# /etc/opt/FJSVsdx/bin/sdxiscsi_ctl -L -e time -c class1Wed Oct 26 19:13:16 2016 |
Node 2
# /etc/opt/FJSVsdx/bin/sdxiscsi_ctl -L -e time -c class1Tue Oct 11 11:34:56 2016 |
The output displays the date and time the cluster application last started on the node where the command was executed.
With the above example, the last started cluster application was on Node 1.
Cancel the lock volume of the netmirror volume.
Take this procedure on both nodes.
# sdxattr -V -c class_name -v volume_name -a lock=off |
Delete the iSCSI device information.
Take this procedure on both nodes.
# rm /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db |
Restore the status of the copy destination disk for the synchronization copying.
Take this procedure on either of both nodes.
For -d option of the sdxswap command, within the disks in the netmirror group, specify the copy destination disk for the synchronization copying.
# sdxswap -O -c class_name -d disk_name |
Start RMS on both nodes.
In this case, the synchronization copying of the netmirror volume is performed.
Restoration Procedure
Stop RMS on both nodes.
If the copy source slice for the synchronization copying is in INVALID, restore the slice state.
For -d option of the sdxfix command, specify the copy source disk for the synchronization copying.
Take this procedure on either of both nodes.
# sdxfix -V -c class_name -v volume_name -d disk_name -x NoRdhk |
-x NoRdchk is the option to skip the read check of the slice. Use this option only for this restoration procedure.
Delete the iSCSI device information.
Take this procedure on both nodes.
# rm /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db |
Perform the synchronization copying.
Take this procedure on either of both nodes.
# sdxcopy -B -c class_name -v volume_name |
Start RMS on both nodes.
