| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.5 The GFS Shared File System Specific Management Commands' Messages |
Execution was attempted with other than super-user permission.
Retry execution with super-user permission.
File open processing for command lock failed.
Apply countermeasures as described in errmsg.
Execution of this command failed as another sfcfrmstart(1M) or sfcfrmstop(1M) command was being executed.
Once execution of the other command has terminated, re-execute this command.
Connection with the cluster control facility failed.
Confirm that the cluster control facility has already been started.
The management partition may be being used on either the self-node or another node.
Wait for the operation of the management partition to end, and then retry.
Memory acquisition failed.
Either wait for another process to end, or increase the size of the swap area.
Setting file sfcfsrm.conf could not be read.
Perform management according to errmsg.
Reading of the management partition failed.
If a disk of the management partition fails, restore the management partition by referring to "9.6 Backup of the management partition information" and "9.7 Restoring of the management partition information".
If a disk failure does not occur, contact your local customer engineers.
The self-node does not belong to a host group.
Using the sfcsetup(1M) command, add the self-node to a host group.
Start processing for sfcfrmd daemon failed.
After confirming the state of the self-node and that sfcprmd daemon is available, contact local Customer Support.
The sfcfrmd daemon has already been started.
None.
As no setting is made to the management partition, the management partition cannot be accessed.
Use the sfcsetup(1M) command to set up the management partition. For details,see "9.2 Creating of the management partition".
The communication path to sfcprmd daemon cannot be established.
After confirming the state of the self-node and that sfcprmd daemon is available, contact local Customer Support.
State confirmation processing for sfcprmd daemon using several different daemons failed.
After confirming the state of self-node and that sfcprmd daemon is available, contact local Customer Support.
Write processing for the management partition failed.
After confirming that no disk error occurred, contact local Customer Supports.
File open processing for editing the sfcfsrm.vers file failed.
Apply countermeasures as described in errmsg.
File write processing for editing the sfcfsrm.vers file failed.
Apply countermeasures as described in errmsg.
File rename processing for editing the sfcfsrm.vers file failed.
Apply countermeasures as described in errmsg.
File access to cancel the suspension of the sfcfrmd daemon startup failed.
Check if the sfcfrmd daemon is running by ps(1) command.
An example is shown below.
# /usr/bin/ps -e | /usr/bin/grep sfcfrmd <Enter> 1629 ? 0:28 sfcfrmd # echo $? <Enter> 0 |
If grep(1)'s return code is 0, sfcfrmd daemon is running.
For details of ps(1) and grep(1) , see the "Solaris X Reference Manual Collection".
If the sfcfrmd daemon is not running, take corrective action according to errmsg. If the error message indicates "broken file", the file to cancel the suspension of the sfcfrmd daemon's startup might be broken. Reboot the system because this file is remade by booting the system.
If sfcfrmd daemon is running, no corrective action needs to be taken because it is thought the sfcfrmd daemon had been started before this file is broken.
Startup of the sfcfrmd daemon has not been suspended.
If the sfcfrmd daemon that is not being suspended is activated, execute the sfcfrmstart(1M) command without the -f option.
The command cannot be executed in the non-global zone.
For Solaris 10 OS, GFS is allowed to be operated in the global zone only.
Collection of the zone setup information failed.
Check the system then wait until the other process is done, or expand the swap area or memory. Execute the command again.
|
Contents
Index
|