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.2 sfcadm and sfcnode commands

E.5.2.1 {sfcadm|sfcnode}:all node entry delete, can't sfcnode

[Explanation]

The command cannot be executed because information about all nodes sharing the file system will be deleted.

[Action]

Reduce the specified host information, and re-execute the command.

E.5.2.2 {sfcadm|sfcnode}:too many host count

[Explanation]

Too many host names were specified.

[Action]

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

E.5.2.3 {sfcadm|sfcnode}:too many partition count

[Explanation]

Too many special files were specified.

[Action]

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

E.5.2.4 {sfcadm|sfcnode}:argument error

[Explanation]

The specified command format is wrong.

[Action]

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

E.5.2.5 {sfcadm|sfcnode}: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.2.6 {sfcadm|sfcnode}:cannot get host information

[Explanation]

The acquisition of host information failed.

[Action]

Confirm that the file system control facility is running normally and that the target host has not failed.

E.5.2.7 {sfcadm|sfcnode}:Cannot connect to FsRM

[Explanation]

The file system control facility is not running.

[Action]

Confirm that file system control facility is running.

E.5.2.8 {sfcadm|sfcnode}:filename cannot open

[Explanation]

Relevant file (filename) does not exist.

[Action]

Confirm if filename is available.

Note that, if the management cannot be found, restore it from a backup or create a new one.

E.5.2.9 {sfcadm|sfcnode}:FSID(fsid_num) is invalid

[Explanation]

File system identification numbers (fsid_num) are not registered in the management partition.

[Action]

Confirm whether the relevant FSID number is registered by using sfcinfo(1M).

E.5.2.10 {sfcadm|sfcnode}:hostid(hostid) not found in volume information

[Explanation]

The specified host ID (hostid) was not found in the partition configuration data.

[Action]

Check whether the specified host ID exists in the partition information.

E.5.2.11 {sfcadm|sfcnode}:invalid hostname

[Explanation ]

An invalid host name was specified.

[Action ]

Check the specified host name.

E.5.2.12 {sfcadm|sfcnode}:hostname(hostname) is not found

[Explanation]

The specified host name (hostname) was not found in the node information.

[Action]

Check whether the specified host name exists in the node information.

E.5.2.13 {sfcadm|sfcnode}:hostname is not shared

[Explanation]

The specified host (hostname) does not share the device.

[Action]

Check the system environment.

E.5.2.14 {sfcadm|sfcnode}: hostname registered as MDS, can't sfcnode -d

[Explanation]

The specified host (hostname) could not delete, because it is registered as the meta-data server.

[Action]

Change the meta-data server host by sfcadm -g.

E.5.2.15 {sfcadm|sfcnode}: invalid devicename

[Explanation]

An invalid partition name was specified.

[Action]

Check whether the specified partition name is correct.

E.5.2.16 {sfcadm|sfcnode}: invalid magic word magic_no

[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.2.17 {sfcadm|sfcnode}: 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.2.18 {sfcadm|sfcnode}:I/O error

E.5.2.19 {sfcadm|sfcnode}:read error (block_no)

E.5.2.20 {sfcadm|sfcnode}:seek error (block_no)

E.5.2.21 {sfcadm|sfcnode}:write error (block_no)

[Explanation]

Special file I/O processing failed.

[Action]

Check whether the specified special file is correct.

E.5.2.22 {sfcadm|sfcnode}:log partition size too small

[Explanation]

The specified log size exceeds the size of the entire log partition.

[Action]

Check the size of the log partition.

E.5.2.23 {sfcadm|sfcnode}:log partition is not separated

[Explanation]

The size could not be changed because the log partition is not separated.

[Action]

Check whether the specified partition is correct.

E.5.2.24 {sfcadm|sfcnode}:logsize is illegal size

[Explanation]

An illegal log size was specified.

[Action]

Check whether the specified log size is correct.

E.5.2.25 {sfcadm|sfcnode}:major number get error

[Explanation]

The major number could not be obtained.

[Action]

Check whether the system environment is correct.

E.5.2.26 {sfcadm|sfcnode}:invalid MDS hostname

[Explanation]

The specification of MDS contains an error.

[Action]

Confirm the management partition and specified MDS information.

E.5.2.27 {sfcadm|sfcnode}:node full, can't {sfcadm | sfcnode}

[Explanation]

The number of nodes sharing the file system exceeded the upper limit.

[Action]

The maximum number of nodes sharing a file system is the value specified for the maxnode parameter in mkfs_sfcfs(1M). If the maximum number will be exceeded, the file system must be reorganized.

E.5.2.28 {sfcadm|sfcnode}: node name length is too long

[Explanation]

The specified node name is too long.

[Action]

Check whether the specified node name is correct. To specify multiple node names, delimit each name by a comma.

E.5.2.29 {sfcadm|sfcnode}:file system configuration information is full of entry

[Explanation]

No more file system information could be added.

[Action]

Delete unnecessary information using sfcadm(1M), and re-execute the command.

E.5.2.30 {sfcadm|sfcnode}:not enough element of sfcfs partition

[Explanation]

Not all the partitions belonging to the file system were specified.

[Action]

Specify all partitions belonging to the file system.

E.5.2.31 {sfcadm|sfcnode}:this node entry not found

[Explanation]

Local node information was not found in the information for nodes sharing the file system.

[Action]

Check whether local node information exists.

E.5.2.32 {sfcadm|sfcnode}:not super user

[Explanation]

The command cannot be executed without super user authority.

[Action]

Execute the command with super user authority.

E.5.2.33 {sfcadm|sfcnode}:not support command

[Explanation]

The executed command is not supported.

[Action]

Check the executed command name.

E.5.2.34 {sfcadm|sfcnode}: ERROR: 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 sfcadm(1M) or sfcnode(1M) again.

E.5.2.35 {sfcadm|sfcnode}:please specify MDS setting

[Explanation]

A meta-data server's host name must be specified.

[Action]

Specify a meta-data server's host name, and re-execute the command.

E.5.2.36 {sfcadm|sfcnode}:please specify PORTNAME setting

[Explanation]

A service port name must be specified.

[Action]

Specify a service port name, and re-execute the command.

E.5.2.37 {sfcadm|sfcnode}:same device is specified more than once

[Explanation]

A partition that is the same as the one specified was found.

[Action]

Check whether the specified partition name is correct.

E.5.2.38 {sfcadm|sfcnode}:invalid service portname

[Explanation]

An invalid service port name was specified.

[Action]

Check the specified service port name.

E.5.2.39 {sfcadm|sfcnode}: file system configuration information sync error

[Explanation]

Distribution to another node sharing the file system failed.

[Action]

Check that a file system watch mechanism works normally, and re-execute the command.

E.5.2.40 {sfcadm|sfcnode}:special cannot open

[Explanation]

A special file (special) could not be opened.

[Action]

Check whether the specified special file is correct.

E.5.2.41 {sfcadm|sfcnode}: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.2.42 {sfcadm|sfcnode}:special is illegal device

[Explanation]

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

[Action]

Specify all partitions configuring the file system.

E.5.2.43 {sfcadm|sfcnode}:special is mounted, can't {sfcadm | sfcnode}

[Explanation]

The command could not be executed because the specified partition (special) has already been mounted. All operations except node information addition with sfcnode(1M) cannot be executed while the partition is mounted.

[Action]

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

E.5.2.44 {sfcadm|sfcnode}: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.2.45 {sfcadm|sfcnode}:special is not sfcfs file system configuration table

[Explanation]

The specified partition (special) does not exist in the management partition.

[Action]

Reexamine whether the specified partition is correct.

E.5.2.46 {sfcadm|sfcnode}: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.2.47 {sfcadm|sfcnode}:system error(function_name)

[Explanation]

A system error occurred.

[Action]

Contact local Customer Support.

E.5.2.48 {sfcadm|sfcnode}:unknown error(ecode)

[Explanation]

An invalid error was detected.

[Action]

Contact local Customer Support.

E.5.2.49 sfcadm: Cannot look up host. Skip check data of it

[Explanation]

The system could not communicate with host name host. sfcadm(1M) continues to update processing of the node and device information in the partition configuration information without checking the data related to host name host. This message is output when sfcadm(1M) is called internally from sfcproxyjoin(1M), sfcproxyop(1M), or sfcproxyrestore(1M).

[Action]

No countermeasures are required for this message, but if you are trying to mount the backup destination file system that was created with sfcproxyop(1M) to the node of host name host after this message is displayed, the mount operation may fail. In this case, mount the file system to a node other than host name host.

E.5.2.50 sfcadm: ERROR: number of mdsnode is over num

[Explanation]

The MDS operational information specified exceeds the number of shared nodes.

[Action]

Specify a value equal to or less than the number of shared nodes or all.

E.5.2.51 sfcnode: ERROR: transit hostname in special is not specified in order in file system configuration table

[Explanation]

The specified partition is the process-ongoing status for node information addition. The status probably occurred because node information addition was not completed due to a system failure or other error.

[Action]

Use sfcinfo(1M) to check whether the partition is the process-ongoing status for node information addition. Then specify the displayed host name (hostname) and re-execute sfcnode(1M).

E.5.2.52 sfcnode: ERROR: special is not mounted on the node in which sfcnode is executed

[Explanation]

sfcnode(1M) cannot be executed because one of the following conditions occurred:

[Action]

Execute one of the following actions:

E.5.2.53 sfcnode: ERROR: hostname is already exist

[Explanation]

The displayed host name (hostname) already exists as a shared node of the target file system.

[Action]

If you are adding node information, check that specified host name is correct.

If you are updating node information, unmount the target file system in all nodes, and then re-execute sfcnode(1M).

E.5.2.54 sfcnode: ERROR: MDS does not support online operation

[Explanation]

The primary MDS does not support addition of shared node information for a mounted file system. Therefore sfcnode failed to add shared node information to the specified file system.

Different versions of the PRIMECLUSTER Global File Services package are probably installed in the node in which sfcnode was executed and the node in which the primary MDS is operating.

[Action]

Make sure that the same version-level of PRIMECLUSTER Global File Services is installed in the nodes of all cluster domains.

You can do this by checking that the output of pkginfo -l FJSVsfcfs are the same on all the cluster domains.

For nodes with different versions (levels) of PRIMECLUSTER Global File Services, install the new package in the node that has the old version-level.

E.5.2.55 sfcnode: ERROR: AC of shared node was blockaded

[Explanation]

The AC is blocked in one of the nodes that share the target file system. Consequently, sfcnode terminated abnormally.

[Action]

The cause of the blockage is reported in an error message that the AC or primary MDS outputs to the console.

Use sfcrscinfo to identify the node in which the AC is blocked and the primary MDS operation node, and then take the action for the output message. Then re-execute sfcnode(1M).

E.5.2.56 sfcnode: Internal error(ecode) strings

[Explanation]

An internal error occurred.

[Action]

Contact local Customer Support.

Contents Index PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004