A.4.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

Opening of the /etc/mtab file failed. The file may be lost.

Response

Recover /etc/mtab then execute the command again.

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

Explanation

A special file special and mount point mount_point were not registered in /etc/mtab.

Response

Check if the values specified are correct.

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

Explanation

A special file special and mount point mount_point were not registered in /etc/mtab.

Response

Check the status of /etc/mtab.

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

Explanation

Memory acquisition failed. System memory is insufficient.

Response

Check the system status then wait for the other process to be completed or expand the swap area or actual memory.

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 like of the ps(1) command (for example, "/bin/ps -e | grep sfcfrmd".), contact field engineers.

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 like of the ps(1) command (for example, "/bin/ps -e | grep sfcfrmd".), contact field engineers.

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 field engineers.

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 like of the ps(1) command (for example, "/bin/ps -e | grep sfcfrmd".), contact field engineers.

ERROR: sfcumount: 0012: special not mounted

Explanation

Special had already been unmounted.

Response

Specify a file system that is being mounted.

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

Explanation

Mount processing had already been performed to special.

Response

When the mount process is completed, unmount the file system again.

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

Explanation

Umount processing had already been performed to special.

Response

After the sfcumount(8) is completed, check if the file system is unmounted.

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 FJQSS, fjsnap, or pclsnap, and collect the kernel dump by push the NMI button and contact field engineers.

ERROR: sfcumount: 0017: special: Umount demand processing to sfcfrmd went wrong

Explanation

The unmount processing request for sfcfrmd failed.

Response

After confirming the state of sfcfrmd by using the like of the ps(1) command (for example, "/bin/ps -e | grep sfcfrmd".), contact field engineers.

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

Explanation

A timeout occurred for the sfcfrmd unmount processing request.

Response

After confirming the state of sfcfrmd by using the like of the ps(1) command (for example, "/bin/ps -e | grep sfcfrmd".), contact field engineers.

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 special file was specified.

Response

Specify the block special file.

ERROR: sfcumount: 0022: special is not block device

Explanation

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

Response

Specify a block special file.

ERROR: sfcumount: 0023: mount_point is not directory

Explanation

The specified mount_point is not a directory.

Response

Change the mount point that is defined in /etc/fstab to the directory path name.

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

Recover /etc/fstab or /etc/mtab then execute the command again.

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 /etc/fstab and /etc/mtab then specify the correct mount point or block special file of the GFS Shared File System for the argument then execute the command again.

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 block special file specified as a mount point was not a representation partition.

Response

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