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

E.4.5 umount_sfcfs command

E.4.5.1 ERROR: umount: 0001: Permission denied

[Explanation]

Execution was attempted with other than super user permission.

[Action]

Retry execution with super user permission.

E.4.5.2 ERROR: umount: 0002: Cannot open mnttab file

[Explanation]

The /etc/mnttab file could not be opened and may be lost.

[Action]

The problem of Solaris OE occurs when generated in the multiuser mode. Please investigate and deal with the message of Solaris OE.

E.4.5.3 ERROR: umount: 0003: Both special and mount_point need to be specified in mnttab

[Explanation]

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

[Action]

Check the arguments.

E.4.5.4 ERROR: umount: 0004: {special | mount_point} not in mnttab

[Explanation]

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

[Action]

Check the arguments.

E.4.5.5 ERROR: umount: 0005: {special | mount_point}: Cannot allocate memory

[Explanation]

Memory acquisition failed. 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.4.5.6 ERROR: umount: 0006: {special | mount_point}: Cannot connect to cluster foundation

[Explanation]

Connection to the cluster control facility failed.

[Action]

Confirm that the cluster control facility has already been started.

E.4.5.7 ERROR: umount: 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.

[Action]

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

E.4.5.8 ERROR: umount: 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 (fsid) within the domain is being obtained with an optional process within the cluster configuration.

[Action]

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

E.4.5.9 ERROR: umount: 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.

[Action]

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

E.4.5.10 ERROR: umount: 0010: {special | mount_point}: Node infomation 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.

[Action]

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

E.4.5.11 ERROR: umount: 0011: {special | mount_point}: sfcfrmd may not exist

[Explanation]

A communication path to sfcfrmd daemon could not be established.

[Action]

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

E.4.5.12 ERROR: umount: 0012: special not mounted

[Explanation]

Special had already been unmounted.

[Action]

None.

E.4.5.13 ERROR: umount: 0013: special: mount is in progress

[Explanation]

Mount processing had already been performed to special.

[Action]

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

E.4.5.14 ERROR: umount: 0014: special: fail over is in progress

[Explanation]

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

[Action]

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

E.4.5.15 ERROR: umount: 0015: special: umount is in progress

[Explanation]

Umount processing had already been performed to special.

[Action]

None.

E.4.5.16 ERROR: umount: 0016: {special | mount_point} busy

[Explanation]

Unmount processing for {special | mount_point} failed.

[Action]

After confirming the state of the special file special or mount point mount_point, contact local Customer Support.

E.4.5.17 ERROR: umount: 0017: device: Umount demand processing to sfcfrmd went wrong

[Explanation]

The unmount processing request for sfcfrmd daemon failed.

[Action]

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

E.4.5.18 ERROR: umount: 0018: device: Time out occurred in umount demand processing to sfcfrmd

[Explanation]

A timeout occurred for the sfcfrmd daemon unmount processing request.

[Action]

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

E.4.5.19 ERROR: umount: 0022: special is not block device

[Explanation]

As the argument of the umount_sfcfs(1M) command, a block device was not specified.

[Action]

Specify a block device.

E.4.5.20 ERROR: umount: 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.

[Action]

Please set time a little and execute a command again.

E.4.5.21 ERROR: umount: 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.

[Action]

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

E.4.5.22 WARNING: umount: 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.

[Action]

None.