| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.4 Command messages for File System Common Management |
Execution was attempted with other than super-user permission.
Retry execution with super-user permission.
Opening of the /etc/mnttab file failed. The file may be lost.
Recover /etc/mnttab then execute the command again.
A special file special and mount point mount_point were not registered in /etc/mnttab.
Check if the values specified are correct.
A special file special and mount point mount_point were not registered in /etc/mnttab.
Check the status of /etc/mnttab.
Memory acquisition failed. System memory is insufficient.
Check the system status then wait for the other process to be completed or expand the swap area or actual memory.
Connection to the cluster control facility failed.
Confirm that the cluster control facility has already been started.
Reading of the management partition to obtain the file system ID failed.
After confirming the state of sfcfrmd daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd".), contact local Customer Support.
Exclusive lock for the file system ID within the domain cannot be obtained. Exclusive lock for the file system ID within the domain is being obtained with an optional process within the cluster configuration.
Try to re-execute after the release of exclusive lock of fsid within the domain.
Reading of the management partition to obtain the cluster configuration node information has failed.
After confirming the state of sfcfrmd daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd".), contact local Customer Support.
Although the management partition containing the cluster node information was read successfully, no self-node information was found to exist.
Check the cluster configuration, and then contact local Customer Support.
A communication path to sfcfrmd daemon could not be established.
After confirming the state of sfcfrmd daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd".), contact local Customer Support.
special had already been unmounted.
Specify a file system that is being mounted.
Mount processing had already been performed to special.
When the mount process is completed, unmount the file system again.
The special file special is being recovered, so the unmount processing failed.
Unmount the file again after completing the down recovery processing.
Unmount processing had already been performed to special.
After the umount_sfcfs(1M) is completed, check if the file system is unmounted.
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 mount_point"). 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 unmount processing request for sfcfrmd daemon failed.
After confirming the state of sfcfrmd daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd".), contact local Customer Support.
A timeout occurred for the sfcfrmd daemon unmount processing request.
After confirming the state of sfcfrmd daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd"), contact local Customer Support.
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).
The character special file was specified.
Specify the block special file.
As the argument of the umount command, a block special file was not specified.
Specify a block special file.
The specified mount_point is not a directory.
Change the mount point that is defined in /etc/vfstab to the directory path name.
An unexpected error was detected in the fstype field in /etc/vfstab or /etc/mnttab.
Recover /etc/vfstab or /etc/mnttab then execute the command again.
The specified file system is not the GFS Shared File System.
Check /etc/vfstab and /etc/mnttab then specify the correct mount point or block special file of the GFS Shared File System for the argument then execute the command again.
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.
|
Contents
Index
|