Explanation
file_name is not executable.
Response
See "Installation Guide" of PRIMECLUSTER and reinstall the package.
Explanation
The status of the GDS volume that was specified as the management partition is not ACTIVE. Or, there is a possibility that the GDS volume is deleted without deleting node configuration information from the management partition by sfcsetup -d on the target node when the use of GFS is stopped.
Response
Check whether the volume exists by executing the following procedures:
# ls -l management_partition <Enter> |
If GFS is used
If the volume does not exist
Create a volume according to the instructions in "Operation" "GDS Management View" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
If there is a backup of the management partition information
Restore the management partition according to the instructions in "9.7 Restoring of the management partition information" in this manual.
If there is no backup of the management partition information
See "9.2 Creating of the management partition" and set up the management partition.
If the volume exists
If the volume status is not ACTIVE, change the status to ACTIVE. For instructions on how to change the volume status, see "Operation" "GDS Management View" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
If GFS is not used
If the volume does not exist
Delete information on the deleted GDS volume by executing the following procedures:
Create a temporary GDS volume of 40 megabytes or more. (GDS volume name is arbitrary)
sfcsetup -c temporary_GDS_volume (GDS volume name made at 1.)
sfcsetup -a temporary_GDS_volume (GDS volume name made at 1.)
sfcsetup -d
If the volume exists
Delete the node configuration information from the management partition by executing the following procedures:
Set the volume status to ACTIVE. For instructions on how to change the volume status, see "Operation" "GDS Management View" in "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
See "9.4 Deleting node configuration information from the management partition"and delete the node configuration information from the management partition.
Explanation
sfcfrmd daemon failed booting.
Response
Check the error message of sfcfrmstart(8) displayed previously to this message, and take corrective action about that message according to "A.5.4 sfcfrmstart command."
Explanation
The daemon could not be stopped.
Response
Collect a file output FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Loading of module failed.
Response
Check if an urgent fix of GFS corresponding to the kernel version of the system is applied.
If the error still exists after applying the fix above, collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Unloading of module failed.
Response
Collect a crash dump and file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
Cluster resource management has not been activated.
Response
Please follow the procedure in an error message of the Cluster resource management output to /var/log/messages. For details, see "PRIMECLUSTER Messages."
Explanation
File access to cancel the suspension of the sfcfrmd daemon's startup failed.
Response
Check that the /var/opt/FJSVsfcfs directory exists. If it does, restart the system. If it doesn't, install the package according to the installation guide.
Explanation
Checking a quorum exists failed.
Response
Check the message of rcqquery(1M) displayed previously to this message, and after taking corrective action about that message according to "rcqquery messages" of "PRIMECLUSTER Messages," restart the system.
Explanation
Activation of the GFS service is disrupted because a quorum does not exist when CF is started by the GUI. If the sfcfrmd daemon's start mode is set to wait, and a quorum does not exist, the GFS service will be discontinued during CF startup.
A quorum does not exist, and the GFS service is discontinued under the following conditions:
CF is activated by the GUI after CF is stopped on all the nodes, then GFS is operated.
A cluster partition error exists.
Response
If you activate CF by the GUI after stopping it on all the nodes, see the procedure described in "12.6 How to start up CF by the GUI when a GFS Shared File System is used."
If you did not stop CF on all the nodes, or the GFS service activation fails after performing the procedure detailed above, a cluster partition error might have occurred. Take corrective action according to "C.3.4 Corrective action when the sfcfrmd daemon is not started."
Explanation
Activation of the sfcfrmd daemon is suspended because a quorum does not exist when the node is started up, the node enters multi-user mode, or CF is started by the GUI. Normally, a quorum be not existing is not maintained until all the nodes are activated. As soon as it is exist, the sfcfrmd daemon will be activated.
Accordingly, it is necessary to take corrective actions under the following conditions otherwise data remains inconsistent.
A cluster partition error exists.
When all the nodes are stopped, or CF is stopped on all the nodes, part of nodes or only CF is activated and then GFS is operated.
Response
Take corrective action according to "C.3.4 Corrective action when the sfcfrmd daemon is not started."
Explanation
Since acquisition of the startup mode of the sfcfrmd daemon fails, the daemon is activated with the wait setting.
Response
If GFS is activated properly, no corrective action needs to be taken. If an error message of the sfcfsrm script is output, it is necessary to take corrective action according to the message.
Explanation
Since a quorum exists, the suspended sfcfrmd daemon was started.
Response
None.
Explanation
Since sfcfrmstart -f was executed, the suspended sfcfrmd daemon was started.
Response
None.
