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.1 sfcadd command

E.5.1.1 sfcadd:/etc/mnttab cannot open

[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.5.1.2 sfcadd: Add another partition is in progress

[Explanation]

The addition of another partition is in progress.

[Action]

Re-execute sfcadd(1M) in 10 minutes.

E.5.1.3 sfcadd: Add transit device, unknown error(ecode)

[Explanation]

An invalid error was detected when an attempt was made to add an entry to the management partition, assuming that the specified partition to be in the process of addition.

[Action]

Contact local Customer Support.

E.5.1.4 sfcadd: An AC of shared node detected disk I/O error

[Explanation]

An AC of a node sharing the file system detected a disk I/O error.

[Action]

Check the partition specified by an argument for normal access from all shared nodes. If a problem does not exist, re-execute sfcadd(1M).

E.5.1.5 sfcadd: An AC of shared node was shut down

[Explanation]

The AC of either one of the nodes that share the file system was shut down.

[Action]

Detailed information is reported by error message sfcfsmg daemon or AC. Apply the countermeasures described in that message. After taking appropriate action, perform mounting, and then re-execute sfcadd(1M).

E.5.1.6 sfcadd: Another file system use specified device.

[Explanation]

The specified partition is being used by another file system.

[Action]

Execute sfcinfo(1M) to confirm a partition not used by another system, then specify the partition and execute sfcadd(1M).

E.5.1.7 sfcadd: argument error

[Explanation]

The specified command format is wrong.

[Action]

Check the command specification format, and re-execute the command.

E.5.1.8 sfcadd: Cannot acquire lock: type(num)

[Explanation]

Cannot get the lock for file system. Other command or daemon is operating with lock.

[Action]

Please wait to complete operating the command or daemon of a GFS Shard file system in all nodes, and re-execute sfcadd(1M) again.

E.5.1.9 sfcadd: Cannot add partition, because special is mounted as readonly

[Explanation]

As the specified file system is mounted in read only mode, sfcadd(1M) cannot be executed.

[Action]

Execute sfcadd(1M) after unmounting, and then perform mounting in other than read only mode.

E.5.1.10 sfcadd: 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.1.11 sfcadd: Cannot get host information

[Explanation]

It failed in the acquisition of host information because the host name and the device name specified by the argument were wrong or the sfcfsrm daemon did not operate.

[Action]

Specify correctly again and execute sfcadd(1M) again when the host name the device name specified by the argument is wrong.

Confirm whether the file system control facility is operating normally while all hosts that share the target file system are activated, and then re-execute sfcadd(1M).

E.5.1.12 sfcadd: Cannot connect to FsRM

[Explanation]

The file system control facility is not operating.

[Action]

Confirm whether the file system control facility is running.

E.5.1.13 sfcadd: '-D' and '-M' are mutually exclusive

[Explanation]

The -D and -M options were specified together.

[Action]

Remove -D option.

E.5.1.14 sfcadd: ERROR: _frm_rmtctl: rmtctl failed. err=num

[Explanation]

It failed in the acquisition of host information in a node sharing the file system.

[Action]

Confirm whether the file system control facility is operating normally while all nodes that share the target file system are activated. Check the partition specified by an argument for normal access from all shared nodes.

E.5.1.15 sfcadd: ERROR: filesystem size is over size terabytes.

[Explanation]

Because the file system size after the partition is added is maximum capacity size or more of file system, partition cannot be added.

[Action]

Decrease the number of the added partitions, or review the size of the partitions added for the file system size after the partitions is added to become less than size.

E.5.1.16 sfcadd: Fail to read disk

[Explanation]

MDS failed to read a disk at a node.

[Action]

For details, see a MDS message on a console.

E.5.1.17 sfcadd: file system configuration table sync error

[Explanation]

Distribution to another node that shares the file system failed.

[Action]

Confirm whether FsRM is running normally, and then re-execute the command.

E.5.1.18 sfcadd: file system (partition-name) is corrupted. To Fix: fsck -F sfcfs partition-name

[Explanation]

sfcadd(1M) cannot be executed because the file system in the specified partition has not terminated normally.

[Action]

Repair the file system using fsck_sfcfs(1M), then re-execute sfcadd(1M).

E.5.1.19 sfcadd: FSID(fsid) is invalid.

[Explanation]

The file system ID number (fsid) of the specified file system is not registered in file system configuration information.

[Action]

Execute sfcinfo(1M) to check a correct file system ID number of the file system.

E.5.1.20 sfcadd: Illegal host in the specified file system.

[Explanation]

The host executing sfcadd(1M) does not belong to the host group of the specified file system.

[Action]

Execute sfcadd(1M) on the host sharing the object file system.

E.5.1.21 sfcadd: Internal error(ecode) strings

[Explanation]

An internal error occurred.

[Action]

Contact local Customer Support.

E.5.1.22 sfcadd: Internal error occurred

[Explanation]

Connection with the file system control facility is disabled.

[Action]

Confirm whether the file system control facility is running normally.

E.5.1.23 sfcadd: invalid magic word 0xmagic

[Explanation]

The partition configuration data of the specified partition is invalid.

[Action]

Check whether the specified partition belongs to an sfcfs file system.

E.5.1.24 sfcadd: ioctl({DKIOCINFO | DKIOCGVTOC}) error

[Explanation]

Device information could not be obtained.

[Action]

Check the system environment to see whether device information is correct.

E.5.1.25 sfcadd: I/O error

[Explanation]

Special file I/O processing failed.

[Action]

This disk cannot be used, use another disk.

E.5.1.26 sfcadd: major number get error

[Explanation]

The major number could not be obtained.

[Action]

Check whether the system environment is correct.

E.5.1.27 sfcadd: No response.

[Explanation]

A timeout is detected during communication with other nodes during the addition.

[Action]

Re-execute sfcadd(1M).

E.5.1.28 sfcadd: Not specified all transit partition names with D option

[Explanation]

All the partitions that remain in the management partition for which addition is in progress are not specified as added devices.

[Action]

According to the contents of the message that is output after this message, specify devicename of all devices that are being added, and then re-execute sfcadd(1M).

E.5.1.29 sfcadd: not super user

[Explanation]

The command cannot be executed without super user authority.

[Action]

Execute the command with super user authority.

E.5.1.30 sfcadd: now locked, can't sfcadd

[Explanation]

sfcadd(1M) cannot be executed because another command is being executed.

[Action]

Upon termination of another command, re-execute the command.

E.5.1.31 sfcadd: number of partitions is over the maximum

[Explanation]

The number of specified partitions exceeded the upper limit.

[Action]

The maximum number of partitions allowed in a file system is the value specified for the maxvol parameter in mkfs_sfcfs(1M). Check whether the number of specified partitions is correct.

E.5.1.32 sfcadd: read error (block_no)

E.5.1.33 sfcadd: read length fewer than expected.

[Explanation]

Special file I/O processing failed.

[Action]

Check whether the specified special file is correct.

E.5.1.34 sfcadd: same device is specified more than once

[Explanation]

The same partition already exists in the specified partition.

[Action]

Check whether the specified partition name is correct.

E.5.1.35 sfcadd: seek error (block_no)

[Explanation]

Special file I/O processing failed.

[Action]

Check whether the specified special file is correct.

E.5.1.36 sfcadd: sharing node is not consistent

[Explanation]

Sharing-node information is inconsistent.

[Action]

Check whether sharing-node information is consistent.

E.5.1.37 sfcadd: special already used as sfcfs file system

[Explanation]

The partition to be added (special) is already being used in the file system.

[Action]

Check whether the specified partition is correct.

E.5.1.38 sfcadd: special cannot open

[Explanation]

A special file (special) could not be opened.

[Action]

Check whether the specified special file is correct.

E.5.1.39 sfcadd: special fstat64 error

[Explanation]

The status of a special file (special) could not be obtained.

[Action]

Check whether the specified special file is correct.

E.5.1.40 sfcadd: special is already defined in file system configuration table

[Explanation]

The specified partition name (special) has already been registered in the file system configuration information.

[Action]

Confirm the information within the management partition. Delete file system information that includes duplicated partitions and then re-execute.

E.5.1.41 sfcadd: special is illegal device

[Explanation]

An illegal partition (special) that is not part of the file system configuration was specified.

[Action]

Specify all partitions configuring the file system.

E.5.1.42 sfcadd: special is mounted from other node

[Explanation]

The specified partition (special) is in a mount state only on other nodes, and cannot perform sfcadd(1M).

[Action]

Re-execute the command, after the file system unmounts in all nodes or in the node that's mounted it.

E.5.1.43 sfcadd: special is mounted, can't sfcadd

E.5.1.44 sfcadd: special is mounted from own other node, can't sfcadd

E.5.1.45 sfcadd: special is other sfcfs file system mounted, can't sfcadd

[Explanation]

sfcadd(1M) could not be executed because the specified partition (special) has already been mounted.

[Action]

Unmount the file system, and re-execute the command.

E.5.1.46 sfcadd: special is not character special device

[Explanation]

The specified file (special) is not a character special file.

[Action]

Specify a character special file.

E.5.1.47 sfcadd: special is not found in file system configuration table

[Explanation]

The specified partition (special) is not available in the management partition.

[Action]

Check whether the specified partition is correct.

E.5.1.48 sfcadd: special is not master partition

[Explanation]

The specified partition name (special) does not indicate the representative partition.

[Action]

Check whether the specified partition is the representative partition.

E.5.1.49 sfcadd: special is not sfcfs file system

[Explanation]

The specified partition (special) does not belong to an sfcfs file system.

[Action]

Check whether the specified partition belongs to an sfcfs file system.

E.5.1.50 sfcadd: special is not shared device

[Explanation]

The specified partition (special) is not shared by nodes.

[Action]

Check whether the system environment is correct.

E.5.1.51 sfcadd: system error(function_name)

[Explanation]

A system error occurred.

[Action]

Check the system environment.

E.5.1.52 sfcadd: too many data partition

[Explanation]

Too many special files were specified.

[Action]

Check whether the number of specified partitions is correct, and re-execute the command.

E.5.1.53 sfcadd: Transit device is exist.

[Explanation]

Failed to delete a transit partition from the file system configuration data.

[Action]

Execute sfcinfo(1M) to check the file system for remaining transit devices. If devices exist, re-execute sfcadd(1M).

E.5.1.54 sfcadd: unknown error(ecode)

[Explanation]

An illegal error was detected.

[Action]

Contact local Customer Support.

E.5.1.55 sfcadd: WARNING: special is already added

[Explanation]

The partition (special) has already been added.

[Action]

A response is not required

E.5.1.56 sfcadd: write error (block_no)

E.5.1.57 sfcadd: write length fewer than expected.

[Explanation]

Special file I/O processing failed.

[Action]

Check whether the specified special file is correct.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004