PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)
Contents Index PreviousNext

Appendix E List of Messages> E.5 Management Command messages Specific to GFS Shared File System

E.5.14 sfcmntgl command

E.5.14.1 ERROR: sfcmntgl: 0001: Permission denied

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Retry execution with super user permission.

E.5.14.2 ERROR: sfcmntgl: 0002: Cannot open vfstab file

[Explanation]

/etc/vfstab could not be opened.

[Action]

Make sure that /etc/vfstab exists. If not, restore it from a backup, or see Section 22.2.3, "Setting vfstab" and redefine it.

E.5.14.3 ERROR: sfcmntgl: 0003: Both special and mount_point need to be specified in vfstab

[Explanation]

Special file special, or mount point mount_point is not described in /etc/vfstab.

[Action]

Check the status of /etc/vfstab.

E.5.14.4 ERROR: sfcmntgl: 0004: {specila | mount_point} not in vfstab

[Explanation]

The specified filename cannot be found in /etc/vfstab.

[Action]

Check the status of /etc/vfstab.

E.5.14.5 ERROR: sfcmntgl: 0005: {specila | mount_point}: Cannot allocate memory

[Explanation]

Memory could not be allocated. Memory of system is insufficient.

[Action]

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.

E.5.14.6 ERROR: sfcmntgl: 0007: {specila | mount_point}: Cannot connect to cluster foundation

[Explanation]

Connection to the cluster service failed.

[Action]

Confirm that the cluster control facility has already been started.

E.5.14.7 ERROR: sfcmntgl: 0008: {special | mount_point}: Cannot get lock: config

[Explanation]

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.

[Action]

Release the lock for changing the domain configuration information, and then re-execute.

E.5.14.8 ERROR: sfcmntgl: 0009: {special | mount_point}: Read error on management partition to get fsid

[Explanation]

Reading of the management partition to obtain the file system id failed.

[Action]

Confirm, using the likes of the ps(1) command, that sfcfrmd daemon is available.

E.5.14.9 ERROR: sfcmntgl: 0010: {specila | mount_point}: Cannot get lock: fsid

[Explanation]

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.

[Action]

Wait for the exclusive lock for fsid to be released, and then retry.

E.5.14.10 ERROR: sfcmntgl: 0011: {special | mount_point}: Read error on management partition to get node infomation

[Explanation]

Reading of the management partition to obtain the cluster configuration node information failed.

[Action]

Confirm, using the likes of the ps(1) command, that sfcfrmd daemon is available.

E.5.14.11 ERROR: sfcmntgl: 0012: special was not able to mount. Other process performed umount or some error occurred. Refer console information on each node for detailed error information.

[Explanation]

Failed to mount special because another node was unmounting it.

[Action]

Unmount it and perform sfcmntgl(1M) command again.

E.5.14.12 ERROR: sfcmntgl: 0013: {specila | mount_point}: sfcfrmd may not exist

[Explanation]

A communications channel with sfcfrmd daemon could not be established.

[Action]

Check whether sfcfrmd daemon is operating using the likes of the ps(1) command, and then contact local Customer Support.

E.5.14.13 ERROR: sfcmntgl: 0018: The description form of vfstab is wrong

[Explanation]

The description format of /etc/vfstab is incorrect.

[Action]

Correct the definition of /etc/vfstab.

E.5.14.14 ERROR: sfcmntgl: 0019: {special | mount_point}: filesystem may not be created

[Explanation]

The specified file system {special | mount_point} was not registered in the management partition.

[Action]

Show a list of all the GFS Shared File System by sfcinfo(1M) command with -a option and make sure that the file system appears that was specified as an argument to sfcmntgl(1M) command.

E.5.14.15 ERROR: sfcmntgl: 0028: {special | mount_point}: hostname is already processing mount or umount

[Explanation]

In the host (hostname), mount or umount processing has already been performed.

[Action]

Please set time a little and execute a command again.

E.5.14.16 ERROR: sfcmntgl: 0029: {special | mount_point}: mount_point need to be representative partition

[Explanation]

The special block device specified as a mount point was not a representation partition.

[Action]

Show a list of all the GFS Shared File System by sfcinfo(1M) command with -a option and find the representative partition. Again perform sfcmntgl(1M) command with the name of the representative partition as an argument.

E.5.14.17 WARNING: sfcmntgl: 0020: hostname: special is already mounted, mount_point is busy, or the allowable number or mount points has been exceeded

[Explanation]

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.

[Action]

Please check the process that is used mountpoint by fuser(1M). Or check the file system that is used mount_point by mount(1M).

E.5.14.18 WARNING: sfcmntgl: 0025: hostname: {special | mount_point}: Send mount demand processing to sfcfrmd went wrong

[Explanation]

Transmission processing for sfcfrmd daemon of the mount processing request made to hostname failed.

[Action]

After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.

E.5.14.19 WARNING: sfcmntgl: 0026: {special | mount_point}: Waiting processing for a response mount demand went wrong

[Explanation]

Reception processing of the mount processing request made to sfcfrmd daemon failed.

[Action]

After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.

E.5.14.20 WARNING: sfcmntgl: 0027: {special |mount_point}: Time out occurred in mount demand processing to sfcfrmd

[Explanation]

A timeout occurred in the reception processing of the mount processing request made to sfcfrmd daemon.

[Action]

After confirming the state of sfcfrmd daemon with the likes of the ps(1) command, contact local Customer Support.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004