PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Linux)
Contents Index PreviousNext

Appendix A List of Messages> A.4 GFS Shared File System Specific Management Command Messages

A.4.10 sfcumntgl command


 

ERROR: sfcumntgl: 0001: Permission denied

[Explanation]

Execution was attempted with other than super-user permission.

[Response]

Retry execution with super-user permission.


 

ERROR: sfcumntgl: 0002: Cannot open fstab file

[Explanation]

/etc/fstab could not be opened.

[Response]

Check the status of /etc/fstab.


 

ERROR: sfcumntgl: 0003: Both special and mount_point need to be specified in fstab

[Explanation]

It needs to be described by /etc/fstab when both the special file special and mount point mount_point are specified as an operand.

[Response]

Check the status of /etc/fstab.


 

ERROR: sfcumntgl: 0004: {special | mount_point} not in fstab

[Explanation]

It was not described by /etc/fstab although {special | mount_point} was specified as a special file or a mount point.

[Response]

Check the status of /etc/fstab.


 

ERROR: sfcumntgl: 0005: device: Cannot allocate memory

[Explanation]

Memory acquisition failed.

[Response]

Either wait for another process to end, or increase the size of the swap area.


 

ERROR: sfcumntgl: 0006: {special | mount_point}: Cannot connect to cluster foundation

[Explanation]

Connection with the cluster control facility failed.

[Response]

Confirm that the cluster control facility has already been started.


 

ERROR: sfcumntgl: 0007: {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.

[Response]

Re-execute after releasing the lock for changing the domain configuration information.


 

ERROR: sfcumntgl: 0008: {special | mount_point}: Read error on management partition to get fsid

[Explanation]

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

[Response]

Confirm, using the likes of the ps command, that sfcfrmd is available.


 

ERROR: sfcumntgl: 0009: device: 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.

[Response]

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


 

ERROR: sfcumntgl: 0010: {special | mount_point}: Read error on management partition to get node information

[Explanation]

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

[Response]

Confirm, using the likes of the ps command, that sfcfrmd is available.


 

ERROR: sfcumntgl: 0011: {special | mount_point}: sfcfrmd may not exist

[Explanation]

A communication path to sfcfrmd could not be established.

[Response]

Confirm, using the likes of the ps command, that sfcfrmd is available.


 

ERROR: sfcumntgl: 0012: hostname: {special | mount_point} busy

[Explanation]

Unmount processing for special file special or mountpoint mount_point failed.

[Response]

In the command execution node, try to find a process that is using the file system by fuser(1) command (for example, "fuser -m mount_point"). If such a process exists, kill the process and unmount the file system again. Otherwise, collect the diagnostic data with pclsnap, and collect the kernel dump by push the NMI button and contact your local Customer Support.


 

ERROR: sfcumntgl: 0013: The description form of fstab is wrong

[Explanation]

The description format of /etc/fstab is incorrect.

[Response]

Confirm the contents of /etc/fstab.


 

ERROR: sfcumntgl: 0019: {special | mount_point}: No such file or directory

[Explanation]

Special file special, or mount point mount_point does not exist.

[Response]

Check whether specified special file and mount point exists on any node.


 

ERROR: sfcumntgl: 0020: {special | mount_point}: stat(2) is error: errmsg

[Explanation]

Obtaining the status of the special file special, or mount point mount_point failed.

[Response]

Take action according to detailed information indicated by errmsg. For details, see the description of stat(2).


 

ERROR: sfcumntgl: 0021: filename: Character device cannot be specified as mount point. Please specify block device

[Explanation]

Character-type special device name filename was specified as the mount point.

[Response]

Specifying a block-type special device name and then re-execute.


 

ERROR: sfcumntgl: 0022: special is not block device

[Explanation]

A block device was not specified as the argument of the sfcumntgl command.

[Response]

Specify a block device.


 

ERROR: sfcumntgl: 0023: mount_point is not directory

[Explanation]

The specified mount_point is not a directory.

[Response]

Check whether specified mount point and described mount point in /etc/fstab is a directory.


 

ERROR: sfcumntgl: 0024: fstype is described as an invalid value in {fstab | mtab}

[Explanation]

An unexpected error was detected in the fstype field in /etc/fstab or /etc/mtab.

[Response]

Check the contents of /etc/fstab or /etc/mtab.


 

ERROR: sfcumntgl: 0025: fstype is described not as sfcfs but as fstype in {fstab | mtab}

[Explanation]

The specified file system is not the GFS shared File System.

[Response]

Check the contents of /etc/fstab and /etc/mtab and specify the GFS Shared File System.


 

ERROR: sfcumntgl: 0029: {special | mount_point}: self-node is already processing mount or umount

[Explanation]

In the self-node, mount or umount processing has already been performed.

[Response]

Please set time a little and execute a command again.


 

ERROR: sfcumntgl: 0030: {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.

[Response]

Please specify a representation partition name and execute a command again.


 

WARNING: sfcumntgl: 0014: device: Cannot get lock: fsid, but processing is continued compulsorily

[Explanation]

Exclusive lock for fsid within the domain could not be acquired, but processing is performed forcibly.

[Response]

None.


 

WARNING: sfcumntgl: 0015: hostname: special not mounted

[Explanation]

special had already been unmounted at hostname.

[Response]

None.


 

WARNING: sfcumntgl: 0016: hostname: special: mount is in progress

[Explanation]

Mount processing had already been performed to special at hostname

[Response]

Either wait a short while and retry the unmount processing, or perform the unmount processing in forced mode.


 

WARNING: sfcumntgl: 0017: hostname: special: fail over is in progress

[Explanation]

Failover processing had already been performed to special at hostname

[Response]

Either wait a short while and retry the unmount processing, or perform the unmount processing in forced mode.


 

WARNING: sfcumntgl: 0018: hostname: special: umount is in progress

[Explanation]

Umount processing had already been performed to special at hostname

[Response]

None.


 

WARNING: sfcumntgl: 0026: hostname: {special | mount_point}: Send umount demand processing to sfcfrmd went wrong

[Explanation]

Transmission of the unmount processing request to sfcfrmd failed with hostname.

[Response]

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


 

WARNING: sfcumntgl: 0027: {special | mount_point}: Waiting processing for a Response umount demand went wrong

[Explanation]

Reception processing of the unmount processing request to sfcfrmd failed.

[Response]

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


 

WARNING: sfcumntgl: 0028: {special | mount_point}: Time out occurred in umount demand processing to sfcfrmd

[Explanation]

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

[Response]

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


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004