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

Appendix A List of Messages> A.4 GFS Shared File System Specific Management Command Messages

A.4.8 sfcsetup command


 

ERROR: sfcsetup: 0001: Permission denied

[Explanation]

Execution was attempted with other than super-user permission.

[Response]

Perform execution with super-user permission.


 

ERROR: sfcsetup: 0002: Cannot connect to cluster foundation

[Explanation]

Communication with the cluster control could not be established.

[Response]

Check whether the cluster control is operating normally.


 

ERROR: sfcsetup: 0003: sfcfrmd is active within cluster foundation

[Explanation]

FsRM is operating within a cluster.

[Response]

Stop FsRM and then re-execute the command.


 

ERROR: sfcsetup: 0004: Cannot get lock: config

[Explanation]

Execution of this command failed as another command was being executed.

[Response]

Once execution of the other command has terminated, re-execute this command.


 

ERROR: sfcsetup: 0005: Too many arguments

[Explanation]

Too many arguments have been specified.

[Response]

Check the command format, and then re-execute.


 

ERROR: sfcsetup: 0006: A few option

[Explanation]

Too few arguments have been specified.

[Response]

Check the command format, and then re-execute.


 

ERROR: sfcsetup: 0007: Wrong command format

[Explanation]

The command format is invalid.

[Response]

Check the command format, and then re-execute.


 

ERROR: sfcsetup: 0008: Cannot get cipname

[Explanation]

The CIP host name for the node executing the command could not be acquired.

[Response]

Check the cluster system settings.


 

ERROR: sfcsetup: 0009: Bad data exists in management partition

[Explanation]

The management partition contain invalid data.

[Response]

Contact local Customer Support.


 

ERROR: sfcsetup: 0010: Cannot write to sfcfsrm.conf

[Explanation]

Writing to the sfcfsrm.conf file failed.

[Response]

Check the status of the sfcfsrm.conf file.


 

ERROR: sfcsetup: 0011: Cannot open management partition

[Explanation]

The management partition could not be opened.

[Response]

Check whether the path to the management partition, specified in the sfcfsrm.conf file, is correct.


 

ERROR: sfcsetup: 0012: Node information area is full

[Explanation]

The maximum possible amount of node information has already been stored.

[Response]

Delete any node information that is no longer necessary, and then re-execute the command.


 

ERROR: sfcsetup: 0013: Cannot write node information

[Explanation]

An error occurred when trying to write new node information.

[Response]

Contact local Customer Support.


 

ERROR: sfcsetup: 0014: Wrong argument format

[Explanation]

The format of an argument specified with the command is invalid.

[Response]

Check the format of the argument, and then re-execute the command.


 

ERROR: sfcsetup: 0015: Invalid argument

[Explanation]

An argument specified with the command contains an invalid character string.

[Response]

Check the argument, and then re-execute the command.


 

ERROR: sfcsetup: 0016: Cannot get lock: master. sfcfrmd may be working now

[Explanation]

The command cannot be executed, either because another command is being executed, or because sfcfrmd is operating.

[Response]

Wait for execution of the other command to terminate or, after executing sfcfrmstop on all the nodes, re-execute the command.


 

ERROR: sfcsetup: 0017: Node(hostid=0xhostid) is busy

[Explanation]

Node (hostid=0xhostid) has still file system information in management partition. It is configured as sharing node of a GFS shared file system. sfcsetup -d did not do anything.

[Response]

Delete node information by following procedures:

  1. Execute sfcfrmstart(8).
  2. Check sharing node information of all GFS shared file system by sfcinfo -an.
  3. Reconfigure sharing node information of GFS shared file system by sfcadm -u, or delete file system information by sfcadm -D.
  4. Execute sfcfrmstop(8).
  5. Retry sfcsetup -d.

 

ERROR: sfcsetup: 0018: Communication initialize error

[Explanation]

Communication could not be initialized.

[Response]

Contact local Customer Support. Or, review your system environment.


 

ERROR: sfcsetup: 0019: socket open error to filename

[Explanation]

A communication channel with the daemon could not be opened.

[Response]

Check that sfcfrmd or sfcprmd are operating normally.


 

ERROR: sfcsetup: 0020: data(data) is not found

[Explanation]

No information could be found for a node that was to be deleted.

[Response]

First check that the input data is correct, and then re-execute the command.


 

ERROR: sfcsetup: 0021: Error occurred. errcode= errcode

[Explanation]

An internal error occurred.

[Response]

Contact local Customer Support.


 

ERROR: sfcsetup: 0022: Cannot allocate memory

[Explanation]

Memory acquisition failed due to a shortage of memory.

[Response]

Terminate any applications that are not required, and then re-execute the command.

Alternatively, review the system environment


 

ERROR: sfcsetup: 0023: Read error of sfcfsrm.conf

[Explanation]

Reading of sfcfsrm.conf failed.

[Response]

Check the status of the sfcfsrm.conf file.


 

ERROR: sfcsetup: 0024: Cannot get status of sfcfrmd on this node

[Explanation]

The process monitor daemon could not acquire the status of the file system recovery manager daemon.

[Response]

Check whether the process monitor daemon is operating normally.


 

ERROR: sfcsetup: 0025: sfcfrmd is active on this node

[Explanation]

The file system recovery manager daemon is running on a node for which an attempt was made to execute a command.

[Response]

Execute sfcfrmstop, and then re-execute the command.


 

ERROR: sfcsetup: 0026: Cluster function may not be working

[Explanation]

The cluster system may not be operating normally

[Response]

Contact local Customer Support.


 

ERROR: sfcsetup: 0027: Input error

[Explanation]

An input error was made.

[Response]

Contact local Customer Support.


 

ERROR: sfcsetup: 0028: raw_device_file is already used as management partition

[Explanation]

The specified character device (raw_device_file) has already been initialized as a management partition.

[Response]

After checking whether this device really should be initialized, re-execute the command with the -f option specified.


 

ERROR: sfcsetup: 0029: Management partition read error

[Explanation]

Reading of the management partition failed.

[Response]

Check the status of the disk containing the management partition.


 

ERROR: sfcsetup: 0030: Management partition write error

[Explanation]

Writing to the management partition failed.

[Response]

Check the status of the disk containing the management partition.


 

ERROR: sfcsetup: 0031: Cannot initialize management partition. errcode=errno

[Explanation]

Initialization of the management partition failed.

[Response]

Check the status of the disk containing the management partition.


 

ERROR: sfcsetup: 0032: raw_device_file is invalid disk device

[Explanation]

Either the specified device (raw_device_file) does not exist, or is not a GDS volume.

[Response]

Check that the specified device is a GDS volume and whether it does, in fact, exist.


 

ERROR: sfcsetup: 0033: Cannot open fstab

[Explanation]

The /etc/fstab file could not be opened.

[Response]

Check the status of /etc/fstab, and whether the file actually exists.


 

ERROR: sfcsetup: 0034: raw_device_file is already exist in fstab

[Explanation]

The device specified (raw_device_file) in the management partition may already be being used by the system.

[Response]

Either specify a different device in the management partition or, if an entry in /etc/fstab is not needed, delete it and then re-execute the command.


 

WARNING: sfcsetup: 0035: Illegal line exists in fstab

[Explanation]

An invalid row is included in /etc/fstab.

[Response]

Confirm the contents of /etc/fstab and correct it if necessary.


 

ERROR: sfcsetup: 0036: Cannot open mtab

[Explanation]

The /etc/mtab file could not be opened.

[Response]

Check the status of the /etc/mtab file and whether it does, in fact, exist.


 

ERROR: sfcsetup: 0037: raw_device_file is already exist in mtab

[Explanation]

The device specified (raw_device_file) in the management partition may already be being used by the system.

[Response]

Either specify a different device in the management partition or, if an entry in the /etc/mtab file is not needed, delete it and then re-execute the command.


 

WARNING: sfcsetup: 0038: Illegal line exists in mtab

[Explanation]

An error occurred while /etc/mtab was being read.

[Response]

Check the contents of /etc/mtab.


 

ERROR: sfcsetup: 0039: Cannot open raw_device_file

[Explanation]

The specified device file (raw_device_file) could not be opened.

[Response]

Check whether the physical connection to the disk is satisfactory.


 

ERROR: sfcsetup: 0040: Cannot get the disk size for the management partition

[Explanation]

The size of the disk on which the management partition resides could not be obtained.

[Response]

Check the status of the disk.


 

ERROR: sfcsetup: 0041: Cannot get major number

[Explanation]

The major number of disk containing the management partition could not be obtained.

[Response]

Check whether the system environment is satisfactory, and whether the specified special file is correct.


 

ERROR: sfcsetup: 0042: Cannot get driver name

[Explanation]

The diver name for the disk containing the management partition could not be obtained.

[Response]

Check whether the system environment is satisfactory, and whether the specified special file is correct.


 

ERROR: sfcsetup: 0043: Cannot get node information

[Explanation]

Node information could not be acquired from the management partition.

[Response]

Check the status and contents of sfcfsrm.conf.


 

ERROR: sfcsetup: 0044: Node information does not exist

[Explanation]

The information for the node for which the command was executed has already been deleted.

[Response]

None.


 

ERROR: sfcsetup: 0045: raw_device_file is not raw_device_file

[Explanation]

The specified device (raw_device_file) is other than a character special device.

[Response]

Check the device name, and then re-execute the command.


 

ERROR: sfcsetup: 0046: Illegal entry exists, or no entry of path to management partition in sfcfsrm.conf

[Explanation]

The sfcfsrm.conf file contains no entry that indicates the path to the management partition. Either node information has not yet been added to the management partition, or it was on a node that has already been deleted.

[Response]

Check whether node information has not yet been added to the management partition, or whether the node containing the entry has already been deleted.


 

ERROR: sfcsetup: 0047: raw_device_file does not exist

[Explanation]

The specified special file (raw_device_file) does not exist in the system environment.

[Response]

Check whether the specified special file is correct.


 

ERROR: sfcsetup: 0048: Too small disk size, need more than 40MB

[Explanation]

The size of the device specified in the management partition is too small.

[Response]

Specify a shared disk with a volume size of 40 MB or more.


 

ERROR: sfcsetup: 0049: Illegal entry exists, or no entry of path to management partition in sfcfsrm.conf

[Explanation]

An invalid row is included in setup file sfcfsrm.conf.

[Response]

Confirm the contents of the setup file sfcfsrm.conf.


 

ERROR: sfcsetup: 0050: Cannot open sfcfsrm.conf: message

[Explanation]

Due to the reason displayed in the message, opening of the FsRM setup file sfcfsrm.conf failed.

[Response]

Apply the countermeasures described in the message.


 

ERROR: sfcsetup: 0051: raw_device_file is not management partition

[Explanation]

The volume of the specified shared disk (raw_device_file) is not initialized for the management partition.

[Response]

Initialize the volume of the shared disk and then re-execute.


 

ERROR: sfcsetup: 0052: sfcfsrm.conf does not exist. sfcsetup may not be executed

[Explanation]

The setup file sfcfsrm.conf cannot be found. Node information may not be registered in the node.

[Response]

Register node information in the management partition by using the sfcsetup command.


 

ERROR: sfcsetup: 0053: Volume(raw_device_file) may not be active. Please activate volume

[Explanation]

The volume of the shared disk that has been specified in the management partition may not be valid.

[Response]

Confirm the state of the volume of the shared disk by executing the sdxinfo(8) command to validate the volume, and then re-execute.


 

INFO: sfcsetup: 0002: Waiting to be able to get lock: master

[Explanation]

The acquisition of domain-wide lock is in progress.

[Response]

Wait for a short while.


 

INFO: sfcsetup: 0003: Waiting to be able to get lock: config

[Explanation]

The acquisition of domain-wide lock is in progress.

[Response]

Wait for a short while.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004