| 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.
Perform execution with super-user permission.
Communication with the cluster control could not be established.
Check whether the cluster control is operating normally.
FsRM is operating within a cluster.
Stop FsRM and then re-execute the command.
Execution of this command failed as another command was being executed.
Once execution of the other command has terminated, re-execute this command.
Too many arguments have been specified.
Check the command format, and then re-execute.
Too few arguments have been specified.
Check the command format, and then re-execute.
The command format is invalid.
Check the command format, and then re-execute.
The CIP host name for the node executing the command could not be acquired.
Check the cluster system settings.
The management partition contain invalid data.
Contact local Customer Support.
Writing to the sfcfsrm.conf file failed.
Check the status of the /var/opt/FJSVgfs/sfcfsrm.conf file.
The management partition could not be opened.
Check whether the path to the management partition, specified in the /var/opt/FJSVgfs/sfcfsrm.conf file, is correct.
The maximum possible amount of node information has already been stored.
Delete any node information that is no longer necessary, and then re-execute the command.
An error occurred when trying to write new node information.
Contact local Customer Support.
The format of an argument specified with the command is invalid.
Check the format of the argument, and then re-execute the command.
An argument specified with the command contains an invalid character string.
Check the argument, and then re-execute the command.
The command cannot be executed, either because another command is being executed, or because sfcfrmd daemon is operating.
Wait for execution of the other command to terminate or, after executing sfcfrmstop(1M) on all the nodes, re-execute the command.
Node (hostid=0xhostid) has still file system information in management partition. It is configured as sharing node of a GFS Shared File System. sfcsetup -d did not do anything.
Delete node information by following procedures:
Communication could not be initialized.
Contact local Customer Support. Or, review your system environment.
A communication channel with the daemon could not be opened.
Check that sfcfrmd daemon or sfcprmd daemon are operating normally.
No information could be found for a node that was to be deleted.
First check that the input data is correct, and then re-execute the command.
An internal error occurred.
Contact local Customer Support.
Memory acquisition failed due to a shortage of memory.
Terminate any applications that are not required, and then re-execute the command.
Alternatively, review the system environment.
Reading of sfcfsrm.conf failed.
Check the status of the /var/opt/FJSVgfs/sfcfsrm.conf file.
The process monitor daemon could not acquire the status of the file system recovery manager daemon.
Check whether the process monitor daemon is operating normally.
The file system recovery manager daemon is running on a node for which an attempt was made to execute a command.
Execute sfcfrmstop(1M), and then re-execute the command.
The cluster system may not be operating normally.
Contact local Customer Support.
An input error was made.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
The block special file special is already being used as a management partition.
If you want to initialize the management partition again, execute the command again with the "-f" option.
Reading of the management partition failed.
Check the status of the disk containing the management partition.
Writing to the management partition failed.
Check the status of the disk containing the management partition.
Initialization of the management partition failed.
Check the status of the disk containing the management partition.
Either the specified device (special) does not exist, or is not a GDS volume.
Check that the specified device is a GDS volume and whether it does, in fact, exist.
The /etc/vfstab file could not be opened.
Check the status of /etc/vfstab, and whether the file actually exists.
The device specified (special) in the management partition may already be being used by the system.
Either specify a different device in the management partition or, if an entry in /etc/vfstab is not needed, delete it and then re-execute the command.
An invalid row is included in /etc/vfstab.
Confirm the contents of /etc/vfstab and correct it if necessary.
The /etc/mnttab file could not be opened. The problem occurs in Solaris OS.
Restore /etc/mnttab, and execute the command again.
The device specified (special) in the management partition may already be being used by the system.
Specify the other special file, or unmount and delete the file then execute the command again.
There is an illegal line in /etc/mnttab.
Recover the contents of /etc/mnttab correctly then execute the command again.
The specified device file (special) could not be opened.
Check whether the physical connection to the disk is satisfactory.
The VTOC information for the disk containing the management information could not be acquired.
Check if the management partition meets all the conditions described in "8.2.1 Setting shared disks". If it does not, configure the management partition again according to "Chapter 5 Management partition". If it does, collect troubleshooting information with fjsnap then contact Fujitsu customer support.
The major number of disk containing the management partition could not be obtained.
Check whether the system environment is satisfactory, and whether the specified special file is correct.
The diver name for the disk containing the management partition could not be obtained.
Check whether the system environment is satisfactory, and whether the specified special file is correct.
Node information could not be acquired from the management partition.
Check the status and contents of /var/opt/FJSVgfs/sfcfsrm.conf.
The information for the node for which the command was executed has already been deleted.
Execute the command on the node which node information will be deleted from config information.
The device special is not a character special file.
Check the device name then execute the command again.
The sfcfsrm.conf file contains no entry that indicates the path to the management partition. Either node information has not yet been added to the management partition, or it was on a node that has already been deleted.
Check whether node information has not yet been added to the management partition, or whether the node containing the entry has already been deleted.
The specified special file (special) does not exist in the system environment.
Check whether the specified special file is correct.
The size of the device specified in the management partition is too small.
Specify a shared disk with a volume size of 40 megabytes or more.
An invalid row is included in setup file sfcfsrm.conf.
An invalid row is included in setup file /var/opt/FJSVgfs/sfcfsrm.conf.
Due to the reason displayed in the message, opening of the FsRM setup file sfcfsrm.conf failed.
Apply the countermeasures described in the message.
The volume of the specified shared disk (special) is not initialized for the management partition.
Initialize the volume of the shared disk and then re-execute.
The setup file sfcfsrm.conf cannot be found. Node information may not be registered in the node.
Register node information in the management partition by using the sfcsetup(1M) command.
The shared disk volume special specified for a management partition may not be ACTIVE.
Check if the shared disk volume is ACTIVE by executing the sdxinfo(1M) command then execute the command again.
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.
The acquisition of domain-wide lock is in progress.
Wait for a short while.
The acquisition of domain-wide lock is in progress.
Wait for a short while.
|
Contents
Index
|