| 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.
/etc/vfstab could not be opened.
Check the status of /etc/vfstab.
It needs to be described by /etc/vfstab when both the special file special and mount point mount_point are specified as an operand.
Correct the definition of the "/etc/vfstab" file system.
It needs to be described by /etc/vfstab when both the special file special and mount point mount_point are specified as an operand.
Check the status of /etc/vfstab.
Memory acquisition failed.
Either wait for another process to end, or increase the size of the swap area.
Connection with the cluster control facility failed.
Confirm that the cluster control facility has already been started.
The lock to change the file system configuration information cannot be obtained. The lock to change the file system configuration information is now being obtained in an optional process of the node within the cluster configuration.
Re-execute after releasing the lock for changing the domain configuration information.
Reading of the management partition to obtain the file system ID failed.
Confirm, using the likes of the ps(1) command, that sfcfrmd daemon is available.
Exclusive lock for fsid within the domain cannot be acquired. The exclusive lock for fsid has been acquired by another process running on a node in the cluster.
Wait for the exclusive lock for fsid to be released, and then retry.
Reading of the management partition to obtain the cluster configuration node information failed.
Confirm, using the likes of the ps(1) command, that sfcfrmd daemon is available.
A communication path to sfcfrmd daemon could not be established.
Confirm, using the likes of the ps(1) command, that sfcfrmd daemon is available.
Unmount processing for special file special or mountpoint mount_point failed.
In the command execution node, try to find a process that is using the file system by fuser(1M) command (for example, "fuser -c special"). If such a process exists, kill the process and unmount the file system again. Otherwise, collect the diagnostic data with fjsnap, and collect the kernel dump by push the NMI button and contact your local Customer Support.
The description format of /etc/vfstab is incorrect.
Confirm the contents of /etc/vfstab.
Special file special, or mount point mount_point does not exist.
Check whether specified special file and mount_point exists on any node.
Obtaining the status of the special file special, or mount point mount_point failed.
Take action according to detailed information indicated by errmsg. For details, see the description of stat(2).
Character-type special device name filename was specified as the mount point.
Specifying a block special file name and then re-execute.
A block special file was not specified as the argument of the sfcumntgl(1M) command.
Specify a block special file.
The specified mount_point is not a directory.
Check whether specified mount point and described mount point in /etc/vfstab is a directory.
An unexpected error was detected in the fstype field in /etc/vfstab or /etc/mnttab.
Restore /etc/vfstab or /etc/mnttab, and re-execute the command.
The specified file system is not the GFS Shared File System.
Check /etc/vfstab and /etc/mnttab then specify a correct mountpoint or block special file of the GFS Shared File System.
In the self-node, mount or umount processing has already been performed.
Please set time a little and execute a command again.
The block special file specified as a mount point was not a representation partition.
Please specify a representation partition name and execute a command again.
special had already been unmounted at hostname.
None.
Mount processing had already been performed to special at hostname.
Either wait a short while and retry the unmount processing.
Failover processing had already been performed to special at hostname.
Either wait a short while and retry the unmount processing.
Umount processing had already been performed to special at hostname.
None.
Transmission of the unmount processing request to sfcfrmd daemon failed with hostname.
After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.
Reception processing of the unmount processing request to sfcfrmd daemon failed.
After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.
A timeout occurred in the reception processing of the unmount processing request made to sfcfrmd daemon.
After confirming the state of sfcfrmd daemon with the likes of the ps command, contact local Customer Support.
|
Contents
Index
|