| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment) |
|
Contents
Index
|
| Appendix E List of Messages | > E.5 Management Command messages Specific to GFS Shared File System |
Sufficient memory could not be acquired. A memory shortfall occurred in the system.
Confirm the state of the system, and then wait until another process terminates or increase the size of the swap area.
Connection to the cluster foundation failed.
Confirm that the cluster foundation has been activated.
You could not establish the communication path to the sfcfrmd daemon.
Use ps(1) to confirm whether the sfcfrmd daemon is running. If it is not running, start the file system monitoring facility by executing the sfcfrmstart(1M) command.
The exclusive lock (name) cannot be acquired because mount, unmount, shutdown, or the file system management command processing for file system change is being executed within the domain of the GFS shared file system.
First of all, please wait to complete all the processing of the file system in the domain of the GFS shared file system like mount, unmount, shutdown, and the file system management command processing for file system change such as sfcswitch(1M), etc. And then re-execute the command.
Opening of the /etc/mnttab file failed. The /etc/mnttab file may have been destroyed.
If this error occurs in multi-user mode, a problem related to Solaris OE has occurred. Check the Solaris OE message and take appropriate corrective action promptly.
Opening of the /etc/vfstab file failed.
Confirm whether /etc/vfstab is available. If it is not present, restore it from the backup or redefine it by referring to "22.2.3 Setting vfstab" in this manual.
The management partition could not be read so that the cluster configuration node information could not be obtained.
Use ps(1) to confirm if the sfcfrmd daemon is running. If it is not running, start the file system monitoring facility by executing the sfcfrmstart(1M) command.
Since hostname has previously failed to start MDS after MDS node start, you cannot start MDS.
After removing the cause of MDS failing to start on hostname, mount the file system again, and then re-execute the command.
An error occurred in stat(2) that is associated with the argument pathname.
Check whether the specified file system is blocked.
If the file system is blocked, you cannot use the file system, and only can unmount it. Collect the diagnostic data with fjsnap and contact local Customer Support.
To restore the target file system, unmount the file system, mount it again, and set a normal operation status. Later, if you want to switch back to the previous file system, execute sfcswitch(1M).
If the file system is not blocked, identify the cause of the I/O error from the console message and apply countermeasures.
Specify a valid operand.
Exclusive lock (name) could not be released because a node that is in the LEFTCLUSTER state is included in the domain.
Resolve the problem with the node that is in the LEFTCLUSTER state, and then re-execute the command.
An invalid entry is registered in the /etc/mnttab file.
Confirm the state of /etc/mnttab by executing the mount(1M) command without specifying any arguments.
If the state cannot be displayed correctly, a problem related to Solaris OE has occurred. Check the mount(1M) command message and any other Solaris OE messages and take a appropriate corrective action promptly.
An entry including an incorrect definition is registered in the /etc/vfstab file.
Confirm whether the specified "detail" includes an error. If no error can be found, correct the setting error in the /etc/vfstab file and then re-execute the command.
An attempt was made to execute the command without super user authority.
Execute the command with super user authority.
Startup of the primary or secondary MDS failed to complete within the specified time.
If MDS is not allocated to the intended node, take corrective action according to the error message output to the console of either node that shares the GFS shared file system and then re-execute the command.
MDS failover processing failed to complete within the specified time.
If MDS is not allocated to the intended node, take corrective action according to the error message output to the console of either node that shares the GFS shared file system and then re-execute the command.
The path name of pathname specified with an argument was different in /etc/vfstab and /etc/mnttab.
If the information in the /etc/mnttab file is correct, correct the /etc/vfstab file setting immediately, and then re-execute the command. To change the setting to match that of the /etc/vfstab file, first unmount the file system. Temporarily restore the setting of the /etc/vfstab file, and then unmount the file system.
The AC is locked out on the hostname node.
First, confirm that the file system is not locked out on any node other than hostname, and then take corrective action according to the message output to the console of the hostname node.
The file system of the specified pathname is not a representative partition name of the GFS shared file system.
Specify a valid pathname, and then re-execute the command.
The file system of the specified pathname is not the GFS shared file system.
Specify a valid pathname, and then re-execute the command.
The specified mount_point is not set to the /etc/vfstab file.
Confirm that the specified mount_point is valid. If no error can be found, check the setting of the /etc/vfstab file, and then re-execute the command.
mount_point is not mounted.
Re-execute the command after you mount mount_point. If it is mounted on a host other than the command execution host, specify special, and then re-execute the command.
You cannot execute the command because the file system is locked out on the hostname node.
Remove the cause of the file system being locked out, and mount the file system again. Then re-execute the command.
Pathname consists of 1024 or more characters.
Check that the path name of the argument is valid. If it is too long, re-specify the path name, being careful not to exceed 1024 characters.
An unidentified reply has been received. This should not happen normally.
Collect debugging information with fjsnap, and then contact your Fujitsu customer engineer (CE.)
A response was not returned from the sfcfrmd daemon within a specified time. This is probably because the sfcfrmd daemon cannot return a response because the sfcfrmd daemon is performing other processing or the load on the node in on which the sfcfrmd daemon is running is too high.
Use the sar(1) command to confirm the high node of CPU or network load on all the nodes on which the file system is mounted. Reduce the load on the node with the high CPU load, and then re-execute the command.
The command cannot be executed because mount, unmount, or MDS down recovery processing is being executed on the target file system.
After confirming the completion of mount, umount, and down recovery processing by sfcinfo(1M), re-execute the command.
MDS was not allocated to the node intended. In addition, since a file system has been mounted on each node, it is unaffected in operation.
Take corrective action according to the message output to the console of either node that shares the GFS shared file system, and then re-execute the command.
The file system was not mounted in the defined P-MDS or S-MDS node. Start MDS on another node on which the file system is mounted to enable operation to continue.
The file system can be operated continuously. Note, however, that you must mount the relevant file system on all the nodes and re-execute the command to start MDS on the defined P-MDS and S-MDS nodes.
The specified options or operand contained one of the following errors:
Specify the options and operands correctly, and then re-execute the command.
|
Contents
Index
|