| 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 if /etc/vfstab exists. If it does not, restore the file from backed up data, or define the file again according to "11.2.3 Setting vfstab".
Special file special, or mount point mount_point is not described in /etc/vfstab.
Check the status of /etc/vfstab.
The specified special or mount_point cannot be found in /etc/vfstab.
Check the status of /etc/vfstab.
Memory acquisition failed.
Either wait for another process to end, or increase the size of the swap area.
Signal handling failed.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
Connection to the cluster service 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.
Release the lock for changing the domain configuration information, and then re-execute.
Reading of the management partition to obtain the file system ID failed.
Confirm, using the likes of the ps 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 command, that sfcfrmd daemon is available.
The mount processing for special file special failed.
Check the status of special file special, and then contact local Customer Support.
A communications channel with sfcfrmd daemon could not be established.
Check whether FsRM is operating, and then contact local Customer Support.
Special file special, or mount point mount_point does not exist.
Check whether specified special 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).
The character device was specified.
Specify the block special file.
The description format of /etc/vfstab is incorrect.
Confirm the contents of /etc/vfstab.
The specified file system {special | mount_point} was not registered in the management partition.
After confirming that the file system has been created, re-execute the sfcmntgl(1M) command.
The specified special is not a block special file.
Check whether specified special file and described special file in /etc/vfstab is 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.
Check the contents of /etc/vfstab.
The specified file system is not the GFS Shared File System.
Check the contents of /etc/vfstab and specify the GFS Shared File System.
In the hostname, 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.
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.
Either special file special has already been mounted in hostname, or mount point mount_point is already in use. Mount processing is not performed for hostname.
None.
Transmission processing for sfcfrmd daemon of the mount processing request made to hostname failed.
After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.
Reception processing of the mount processing request made to sfcfrmd daemon failed.
After confirming the state of sfcfrmd daemon with the likes of the ps command, contact local Customer Support.
A timeout occurred in the reception processing of the mount 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
|