A.5.2 sfcadd command

sfcadd: ERROR: 0001: not super user

Explanation

Execution was attempted with other than super-user permission.

Response

Retry execution with super-user permission.

sfcadd: ERROR: 0002: 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.

sfcadd: ERROR: 0003: the number of partitions exceeded the maximum number

Explanation

Adding a partition failed because the number of partitions specified exceeds the upper limit. The upper limit of the number of partitions that can configure the file system is the value specified with the maxvol parameter of sfcmkfs(8). The upper limit cannot be changed.

Response

Specify the upper limit or less and execute the command again.

sfcadd: ERROR: 0004: same device is specified more than once

Explanation

The same partitions exists in the partition specified.

Response

Check if the specified partition is correct.

sfcadd: ERROR: 0005: cannot connect to FsRM

Explanation

The file system monitoring mechanism is not operating.

Response

Confirming the state of sfcfrmd by using the likes of the ps(1) command. If it does not, activate the file system monitoring facility by executing the sfcfrmstart(8).

sfcadd: ERROR: 0006: unknown error(errnum)

Explanation

An error is detected.

Response

Check if the DNS settings are correct. If they are, collect troubleshooting information with FJQSS, fjsnap, or pclsnap the contact field engineers.

sfcadd: ERROR: 0007: cannot acquire lock: name(errnum)

Explanation

Acquisition of the file system lock failed. The other command has acquired the lock.

Response

Wait until the management command of the GFS Shared File System to be completed on all the cluster nodes then execute the command again.

sfcadd: ERROR: 0008: cannot read management partition

Explanation

Reading of the management partition failed.

Response

Check if the management partition is set using the sfcsetup(8) command.
If it is not, set the management partition using sfcsetup(8). If it is, collect troubleshooting information with FJQSS, fjsnap, or pclsnap the contact field engineers.

sfcadd: ERROR: 0009: special is already used for the management partition

Explanation

The special file special cannot be used because it is being used as a management partition.

Response

Specify the other partition and execute the command again.

sfcadd: ERROR: 0010: file system configuration information not found

Explanation

Acquisition of the file configuration failed.

Response

Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.

sfcadd: ERROR: 0011: special is not found in file system configuration table

Explanation

The special file special does not exist in the management partition.

Response

Check whether the specified partition is correct.

sfcadd: ERROR: 0012: fsid(num) is invalid

Explanation

The identifier number num of the specified file system is not registered.

Response

Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.

sfcadd: ERROR: 0013: special is illegal device

Explanation

The special file special specified is nonexistent.

Response

Check if the special file special exists.

sfcadd: ERROR: 0014: special is not block special device

Explanation

The specified special is not a block special file.

Response

Specify the block special file.

sfcadd: ERROR: 0015: special already used as sfcfs file system

Explanation

The partition special is already being used for the GFS Shared File System.

Response

Specify a partition that is not used for the GFS Shared File System.

sfcadd: ERROR: 0016: shared nodes of special is inconsistent

Explanation

A shared node of the specified file system is not included in the scope of the disk class to which GDS logical volume of special belongs.

Response

Specify GDS logical volume that belongs to the disk class that includes all shared nodes of the specified file system in the scope to special.

sfcadd: ERROR: 0017: special is mounted, can't sfcadd

Explanation

The special file special is being mounted, so the sfcadd(8) cannot be executed.

Response

Unmount the special file special then execute the command again.

sfcadd: ERROR: 0018: special is mounted from other node

Explanation

The special file special is being mounted on the other node, so the sfcadd(8) cannot be executed.

Response

Unmount the special file special then execute the command again.

sfcadd: ERROR: 0019: special cannot open

Explanation

Opening of the special file special failed.

Response

Check if the special file special is correct.

sfcadd: EROOR: 0020: special fstat64 error

Explanation

Acquisition of the special file special failed.

Response

Check if the special file special is correct.

sfcadd: ERROR: 0022: special is already used for other file system

Explanation

The additional partition special is described in /etc/fstab.

Response

Check the "/etc/fstab" file. If the partition special is added, delete special from /etc/fstab.

sfcadd: ERROR: 0023: /etc/mtab cannot open

Explanation

Opening of /etc/mtab failed.

Response

Recover /etc/mtab then execute the command again.

sfcadd: ERROR: 0024: /etc/fstab cannot open

Explanation

Opening of /etc/mtab failed.

Response

Check if /etc/fstab exists. If it does not, restore the file from backed up data, or define the file again according to "11.2.4 Setting fstab."

sfcadd: ERROR: 0025: cannot read /etc/fstab

Explanation

There is an invalid line in /etc/fstab.

Response

Modify the "/etc/fstab" file.

sfcadd: ERROR: 0026: special partition size is over the maximum file system capacity

Explanation

The size of the partition special exceeds the maximum file system size.

Response

Set the size of the partition special not to exceed the maximum file system size, or specify the other partition.

sfcadd: ERROR: 0027: special ioctl{(BLKGETSIZE)|(DKIOCGVTOC)|(DKIOCINFO)} error

Explanation

Acquisition of the device special failed.

Response

Check if a disk I/O error is output then take corrective action according to the error message.

sfcadd: ERROR: 0028: special is not representative partition

Explanation

Special is not a representative partition.

Response

Specify a representative partition for operand.

sfcadd: ERROR: 0029: special cannot read super block

Explanation

Reading of the special super block failed.

Response

Recover the file system using sfcfsck(8). If the message "special is clean" is output, recover the file system by executing sfcfsck(8) with the options -o, f, and nolog. If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0030: special is not sfcfs file system

Explanation

Special is not of the GFS Shared File System.

Response

Recreate the file system then restore the backed up data.

sfcadd: ERROR: 0031: special cannot write super block

Explanation

Writing of the special super block failed.

Response

If special is the specified additional partition, recover failed parts, or prepare the other partition then specify it to execute the command.

If special is a partition that configures the file system, recover the file system by executing sfcfsck(8) with the options -o, f, and nolog. If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0032: special is invalid disk device

Explanation

Special is not of the GFS Shared File System.

Response

Specify a GDS volume.

sfcadd: ERROR: 0033: total file system size is too large

Explanation

If the specified partition is added, the file system size will exceed the maximum file system size, so the partition cannot be added.

Response

Specify a partition where the file system size will not exceed the maximum file system size.

sfcadd: ERROR: 0034: special cannot write volume information

Explanation

Writing of the special partition configuration failed.

Response

If special is the specified additional partition, recover failed parts, or prepare the other partition then specify it to execute the command.

sfcadd: ERROR: 0035: special super block restore failed

Explanation

Recovering of the special super block failed.

Response

Copy the super block of the representative partition to the partition that configures the file system by executing sfcadm(8). Then, recover the file system by executing sfcfsck(8) with the options -o, f, and nolog. If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0036: device number of special and special is the same

Explanation

special and the device number of special are the same.

Response

Check if the specified partition is correct.

sfcadd: ERROR: 0037: cannot update meta area

Explanation

Updating the meta-data area failed.

Response

sfcadd: ERROR: 0038: meta area restore failed

Explanation

Recovering the meta-data area failed.

Response

Recreate the file system then restore the backed up data.

sfcadd: ERROR: 0039: file system (special) is corrupted. To Fix: sfcfsck special

Explanation

sfcadd(8) cannot be executed because the state of the file system of the partition special was not stopped properly.

Response

Recover the file system using sfcfsck(8). If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0040: special volume information restore failed

Explanation

Recovering of the special partition configuration failed.

Response

Copy configuration information of the representative partition to the partition that configures the file system by executing sfcadm(8). Then, recover the file system by executing sfcfsck(8) with the options -o, f, and nolog. If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0041: special cannot read volume information

Explanation

Reading of special partition configuration information failed.

Response

Recover the file system by executing sfcfsck(8) with the options -o, f, and nolog. If the file system cannot be recovered due to a disk device failure, recover the failed part then recreate the file system and restore the backed up data.

sfcadd: ERROR: 0042: cannot read /etc/mtab

Explanation

Reading of the /etc/mtab file failed.

Response

Recover the /etc/mtab file then execute the command again.

sfcadd: ERROR: 0043: cannot get host informations

Explanation

The sfcfrmd daemon of the node that shares the file system has not been activated.

Response

Check if the sfcfrmd daemon exists by executing the ps(1) command on all the nodes that share the file system. The nodes can be checked with sfcinfo(8).
If the nodes are stopped, start them. If the sfcfrmd daemon does not exist, activate the daemon using sfcfrmstart(8) on the node.
If it does, collect troubleshooting information using FJQSS, fjsnap, or pclsnap then contact field engineers.

sfcadd: ERROR: 0044: cannot read sfcfsrm.conf

Explanation

Reading of the setup file /var/opt/FJSVsfcfs/sfcfsrm.conf failed.

Response

Recover the system in the event of a disk failure. If a disk failure does not occur, collect troubleshooting information using FJQSS, fjsnap, or pclsnap then contact field engineers.

sfcadd: ERROR: 0045: file system (special) is not shared for this node

Explanation

The command is executed on the node that does not share the file system.

Response

Execute the command on the node that shares the file system.