| 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 |
Execution was attempted with other than super user permission.
Retry execution with super user permission.
/etc/vfstab could not be opened.
Make sure that /etc/vfstab exists. If not, restore it from a backup, or see Section 22.2.3, "Setting vfstab" and redefine it.
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 entry of /etc/vfstab, and see Section 22.2.3, "Setting vfstab" and redefine it.
It was not described by /etc/vfstab although {special | mount_point} was specified as a special file or a mount point.
Check the status of /etc/vfstab.
Memory could not be allocated. Memory of system is insufficient.
Please check the state of a system, and wait for the termination of another process, or increase the swap space or real memory. After it and re-execute the command.
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 | mount_point} failed with hostname.
In the node hostname, try to find a process that is using the file system by fuser(1M) command (for example, "fuser -c hostname".) If such a process exists, kill the process and unmount the file system again.
The description format of /etc/vfstab is incorrect.
Confirm the contents of /etc/vfstab.
The special file special or the mount point mount_point cannot be found.
Specify the path name that exists as the special special file or the mount_point mount point.
Character-type special device name filename was specified as the mount point.
Specifying a block-type special device name and then re-execute.
A block device was not specified as the argument of the sfcumntgl(1M) command.
Specify a block device.
In the self-node, mount or umount processing has already been performed.
Please set time a little and execute a command again.
The special block device specified as a mount point was not a representation partition.
Show a list of all the GFS Shared File System by sfcinfo(1M) command with -a option and find the representative partition. Again perform sfcumntgl(1M) command with the name of the representative partition as an argument.
Exclusive lock for fsid within the domain could not be acquired, but processing is performed forcibly.
None.
Mount processing had already been performed to special at hostname
Either wait a short while and retry the unmount processing, or perform the unmount processing in forced mode.
Failover processing had already been performed to special at hostname
Either wait a short while and retry the unmount processing, or perform the unmount processing in forced mode.
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(1) command, contact local Customer Support.
|
Contents
Index
|