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

Appendix A List of Messages> A.3 GFS Shared File System Exclusive Management Command Messages

A.3.5 sfcumount command


 

ERROR: sfcumount: 0001: Permission denied

[Explanation]

Execution was attempted with other than super-user permission.

[Response]

Retry execution with super-user permission.


 

ERROR: sfcumount: 0002: Cannot open mtab file

[Explanation]

/etc/mtab could not be opened.

[Response]

Check the status of /etc/mtab.


 

ERROR: sfcumount: 0003: Both special and mount_point need to be specified in mtab

[Explanation]

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

[Response]

Check the status of /etc/mtab.


 

ERROR: sfcumount: 0004: {special | mount_point} not in mtab

[Explanation]

Although a special file or {special | mount_point } has been specified for the mount point, neither is described in /etc/mtab.

[Response]

Check the status of /etc/mtab.


 

ERROR: sfcumount: 0005: {special | mount_point}: Cannot allocate memory

[Explanation]

Memory acquisition failed.

[Response]

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


 

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

[Explanation]

Connection to the cluster control facility failed.

[Response]

Confirm that the cluster control facility has already been started.


 

ERROR: sfcumount: 0007: {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]

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


 

ERROR: sfcumount: 0008: {special | mount_point}: Cannot get lock: fsid

[Explanation]

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.

[Response]

Try to re-execute after the release of exclusive lock of fsid within the domain.


 

ERROR: sfcumount: 0009: {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 has failed.

[Response]

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


 

ERROR: sfcumount: 0010: {special | mount_point}: Node information for this node was not found

[Explanation]

Although the management partition containing the cluster node information was read successfully, no self-node information was found to exist.

[Response]

Check the cluster configuration, and then contact local Customer Support.


 

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

[Explanation]

A communication path to sfcfrmd could not be established.

[Response]

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


 

ERROR: sfcumount: 0012: special not mounted

[Explanation]

Special had already been unmounted.

[Response]

None.


 

ERROR: sfcumount: 0013: special: mount is in progress

[Explanation]

Mount processing had already been performed to special.

[Response]

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


 

ERROR: sfcumount: 0014: special: fail over is in progress

[Explanation]

Unmount processing was attempted as failover processing was being performed for special.

[Response]

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


 

ERROR: sfcumount: 0015: special: umount is in progress

[Explanation]

Umount processing had already been performed to special.

[Response]

None.


 

ERROR: sfcumount: 0016: {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: sfcumount: 0017: device: Umount demand processing to sfcfrmd went wrong

[Explanation]

The unmount processing request for sfcfrmd failed.

[Response]

Check the status of sfcfrmd, and then contact local Customer Support.


 

ERROR: sfcumount: 0018: device: Time out occurred in umount demand processing to sfcfrmd

[Explanation]

A timeout occurred for the sfcfrmd unmount processing request.

[Response]

Check the status of sfcfrmd, and then contact local Customer Support.


 

ERROR: sfcumount: 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: sfcumount: 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: sfcumount: 0021: special: Character device can not be specified as mount point. Please specify block device.

[Explanation]

The character device was specified.

[Response]

Specify the block device.


 

ERROR: sfcumount: 0022: special is not block device

[Explanation]

As the argument of the umount command, a block device was not specified.

[Response]

Specify a block device.


 

ERROR: sfcumount: 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: sfcumount: 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: sfcumount: 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: sfcumount: 0027: {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: sfcumount: 0028: {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: sfcumount: 0026: {special | mount_point}: Cannot get lock: fsid, but processing is continued compulsorily

[Explanation]

Although exclusive lock could not be acquired for fsid within the domain, processing was performed forcibly.

[Response]

None.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004