| 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.
/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.
Connection to the cluster control facility failed.
Confirm that the cluster control facility has started.
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.
Signal handling failed.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
The lock to change the file system (mount_point) configuration information cannot be obtained. In an optional process within the cluster configuration, the lock to change the file system configuration information is being obtained.
Execution must be performed after waiting for the lock to change the domain configuration information to be released.
Reading of the management partition to obtain the file system (mount_point) id 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.
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 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.
The node is not set as a member of sharing the GFS Shared File System.
Check node information by executing the sfcinfo(1M) with the -an option. If the host name is missing, add it by executing sfcnode(1M). If the host name is incorrect, correct it by executing sfcadm(1M).
Mount processing for special failed.
Check the status of the specified special file and mount point, and check whether the mount option described by /etc/vfstab is correct. Then retry mount processing.
A communications channel with 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 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).
Special file special may have already been mounted, or the mount point mount_point may be in use.
Check if some process is using mount_point by executing fuser(1M), and if it is, stop the process to use the mount point. If the special file is already mounted, unmount it.
Mount processing request to daemon 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.
Timeout occurred for a mount processing request to sfcfrmd daemon.
After confirming the state of daemon by using the like of the ps(1) command (for example, "/usr/bin/ps -e | /usr/bin/grep sfcfrmd".), contact local Customer Support.
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.
The description format of /etc/vfstab is incorrect.
Confirm the contents of /etc/vfstab.
The specified file system was not registered in the management partition.
After confirming that the file system has already been created, re-execute the mount_sfcfs(1M) command.
In the self-node, mount or umount processing has already been performed.
When mounting or unmounting of the file system is completed, execute the 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.
Although mount option mntopts has been specified as the mount command parameter, mount processing was performed with mount option vfs_mntopts, described by /etc/vfstab.
If you want to mount the file system using a mount option, set the mount point in the file system definition of /etc/vfstab.
Although mount option mntopts has been adopted as the mount command parameter, it was ignored and mount processing was performed with no parameters.
To specify the mount option and perform mount processing, describe the mount option for the mount point in question in /etc/vfstab.
|
Contents
Index
|