Explanation
The specified configuration is not the same as the configuration of the previously created file system.
Response
When specifying the -o force option, specify the same configuration as that of the previously created file system and re-execute the command.
Explanation
A failure occurred because all communication port numbers have been used.
Response
Add a new communication port number for sfcfs to /etc/services.
Explanation
Connecting to the cluster control facility failed.
Response
Make sure that the cluster control facility is operating using the ps command, and re-execute the command.
Explanation
Specified special was not found.
Response
Check whether the specified special file name is correct, and re-execute the command.
Explanation
Opening the file filename failed.
Response
Check whether the file filename exists, and re-execute the command.
Explanation
The file data area is not sufficient in size, and therefore, a file system cannot be created.
Response
Review parameters so that a sufficiently large file data area can be reserved.
Explanation
Opening the special file filename failed.
Response
Take action according to the detailed information errmsg.
Explanation
Updating the file system configuration information failed.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of errmsg.
Explanation
An illegal option was specified.
Response
Specify a correct option and argument.
Explanation
The update log area cannot be created because the representative partition is too small.
Response
Check the specified parameter, allocate enough space for the representative partition, and re-execute the command.
Explanation
The meta-data area cannot be created because the representative partition is too small.
Response
Review the specified parameter, secure sufficient space on the representative partition, and re-execute the command.
Explanation
The user executing this command is not a super-user.
Response
Re-execute the command as a super-user.
Explanation
The number of specified sharing hosts exceeds the maximum num for GFS Shared File System.
Response
Specify no more than num hosts that will share the file system.
Explanation
No corresponding file system exists while the -o force option was specified.
Response
Specify the same configuration as the file system configuration previously created the -o force option should be set, and re-execute the command.
Explanation
The number limit of registrable GFS Shared File Systems was exceeded, and any more file system cannot be added.
Response
Delete an unnecessary GFS Shared File System where it is possible and re-execute the command. For details about deleting a file system, see sfcadm(8) and sfcinfo(8).
Explanation
The specified host name indicated by string has already been specified.
Response
Specify a unique host name for the -o node option.
Explanation
Obtaining the status of the special file special failed.
Response
Take action according to detailed information indicated by errmsg. For details, see the description of fstat(2).
Explanation
Obtaining the device size failed.
Response
Take action according to the detailed information errmsg.
Explanation
lseek(2) could not be executed for special.
Response
Take action according to detailed information indicated by errmsg. For details, see the description of lseek(2).
Explanation
Memory could not be allocated.
Response
Wait for the termination of another process or increase the swap space according to the detailed information errmsg.
Explanation
The specified special device special has been used in another GFS Shared File System.
Response
Re-execute the command after taking one of the following actions:
Use an unused special device.
Delete the file system if it is not being used.
Specify -o force to re-create a file system with exactly the same configuration.
Explanation
The number limit of registrable GFS Shared File Systems was exceeded, and any other file system cannot be added in filetable.
Response
Delete an unnecessary GFS Shared File System where it is possible and re-execute the command. For details about deleting a file system, see sfcadm(8) and sfcinfo(8).
Explanation
The specified partition indicated by special cannot be changed because the file system is mounted.
Response
Unmount the file system and re-execute the command specifying -o force, or delete the file system with sfcadm(8) and re-execute the command.
Explanation
The special device special is not a GFS Shared File System device while the -m option was specified.
Response
Specify a special file created already as a GFS Shared File System, and re-execute the command.
Explanation
Specified special is not a special device file.
Response
Specify a special file.
Explanation
read(2) for special failed.
Response
Take action according to detailed information indicated by errmsg. For details, see the description of read(2).
Explanation
The write(2) operation for special failed.
Response
Take action according to detailed information indicated by errmsg. For details, see the description of write(2).
Explanation
An error was detected in the internal processing.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
The size of the partition of special has exceeded 1 terabyte.
Response
Reduce the size of special or specify another partition when it is exceeding the maximum partition size, and re-execute the command.
Explanation
An internal error was detected in the process of newly adding a file system.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
Memory allocation failed.
Response
Wait for the termination of another process or increase the swap space.
Explanation
Obtaining the file system configuration information failed.
Response
Collect a file output with FJQSS, fjsnap, or pclsnap for troubleshooting information then contact field engineers.
Explanation
An internal error was detected in the process of newly adding a file system.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
Obtaining the lock in the file system failed.
Response
Re-execute the command after some interval because another process may currently retain the lock.
Explanation
Releasing the lock in the file system failed.
Response
Re-execute the command after the sfcmkfs termination releases the lock.
Explanation
Obtaining Fsid for newly adding a file system failed.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
Obtaining the lock in the domain failed.
Response
Re-execute the command after some interval because another process may currently retain the lock.
Explanation
Specified special has been used for the file system management.
Response
Specified special is not available because it is in use for the file system management.
Specify another special file to execute the command.
Explanation
An internal error was detected in the process of newly adding a file system.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
Obtaining the file system configuration information of fsidnumber failed.
Response
Specify the same configuration as the file system configuration previously created where the -o force option is set, or specify the representative partition of the file system configured already where the -m option is set.
Explanation
special is not the representative partition.
Response
Specify the representative partition of the file system created already.
Explanation
An error was detected in the internal processing.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
An error was detected in the internal processing with the cluster control facility.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
The specified special file is not found.
Response
Check whether the special file exists on any node of the file system.
Explanation
Securing the file data area failed because the size of the partition special is small.
Response
Specify the bigger partition for special or adjust such parameters as metasz and logsz for smaller size in order to secure the file data area, and re-execute the command.
Explanation
Obtaining the FsRM management information failed.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
Acquisition of host information of the specified node failed.
Possible causes:
The node specified is invalid.
The network setting of the specified node is invalid.
The specified node is stopped.
sfcfrmd daemon is not running on the specified nodes.
A cluster partition error exists.
Response
Execute sfcmkfs(8) again after correcting the cause of the failure according to the following procedures.
Check whether the node specified is correct. If a mistake is found, specify the correct host name.
On the specified node, check whether the IP address of the specified node is correctly registered in host database (such as /etc/hosts). For details, see "11.2.2 Registering information in host database" in this manual.
Confirm that the specified node is not stopped. If the node was stopped, start it.
Execute the following operations on all the specified nodes.
Check if the sfcfrmd daemon is operating by ps(1) command.
An example is shown below.
# /bin/ps -e | /bin/grep sfcfrmd <Enter> 27198 ? 00:00:00 sfcfrmd # echo $? <Enter> 0 |
If grep(1)'s return code is 0, sfcfrmd daemon is running.
See
For details of ps(1) and grep(1), see the online manual page.
If the sfcfrmd daemon is not running, confirm that the following message is not output to /var/log/messages.
WARNING: sfcfsrm:5001: Starting the sfcfrmd daemon was suspended because quorum does not exist |
If the message is not output, execute sfcfrmstart(8) command.
When a problem can not be resolved using operations from 1 to 4, a cluster partition error may have occurred. Correct the cluster partition error according to "C.3.4 Corrective action when the sfcfrmd daemon is not started."
Explanation
Registration to the file system management information failed.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
An unexpected error was detected in the internal processing.
Response
Collect the diagnostic data with FJQSS, fjsnap, or pclsnap, and contact field engineers submitting it along with text of the error message displayed.
Explanation
The number of partitions specified exceeds the upper limit count specified with the maxvol option.
Response
Increase the value of the maxvol option or decrease the number of partitions configuring the file system by grouping the partitions.
Explanation
A partition same as the file data partition specified with -o data or same as a representative partition specified with an operand is being used.
Response
Specify a file data partition with -o data only once, or specify a representative partition with an operand different than that specified with -o data.
Explanation
The total of specified partition sizes exceeds the maximum file system size, so a file system cannot be created.
Response
Make sure that the total of partition sizes of the file data partition specified with -o data and the representative partition specified with operand is less than the maximum file system size.
Explanation
The configuration of the specified partition is different than that of the current partition, so a file system cannot be recreated.
Response
Check the configuration of the current partition using the "sfcmkfs -m" command. To make the configuration of the specified partition same as that of the displayed current partition by executing sfcmkfs(8) with the "-o data" option and correct operand.
Explanation
The parameter value, value, specified by the logsz option lies outside the valid range, and the value is automatically calculated to create the file system.
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The value of the maxnode option is out of the valid range, so the default value 16 will be used to create a file system.
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The value value specified for the metasz option is outside the valid range. The file system is created using a calculated size.
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The value value specified for the mfree option is outside the valid range. The file system is created using the default value (10%).
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The value value specified for the nblkpext option is outside the valid range. The file system is created using the default value (1).
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The value value specified for the nbpi option is outside the valid range. The file system is created using the default value (8192).
Response
If there is a problem, specify a correct parameter value, and re-execute the command.
Explanation
The log area of the size (value) specified by the logsz option cannot be secured because the capacity of the partition is insufficient. The log area size is automatically calculated to create the file system.
Response
When this action comes to an issue, specify a proper parameter value and re-execute the command.
Explanation
The meta-data area of the size (value) specified by the metasz option cannot be secured because the capacity of the partition is insufficient. The meta-data area size is automatically calculated to create the file system.
Response
When this action comes to an issue, specify a proper parameter value and re-execute the command.
Explanation
The parameter value, value, specified by the free option lies outside the range, and the default value 10% is applied to create the file system.
Response
When this action comes to an issue, specify a proper parameter value and re-execute the command.
Explanation
As the specified value value of the maxdsz option is out of the valid range or is small for the specified file system configuration, the file system is created, assuming that the maxdsz option is omitted.
Response
The meta-data area size and update log area size of the created file system is calculated from the file system size of the specified partition. No corrective action should be taken if this configuration is used.
If it is assumed to add file data partitions to the file system in the future, delete the file system using sfcadm(8).
Then, specify the maximum total size of the file data area in case of expanding area by adding file data partitions in the "-o maxdsz" of sfcmkfs(8) and execute the command again.
Explanation
As the specified value value of the maxvol option is out of the valid range, the default value 16 will be used to create a file system.
Response
The maximum number of partitions of the file system is 16. No corrective action should be taken if this configuration is used.
If it is assumed that the number of partitions of the file system exceeds 16 in the future, delete the file system using sfcadm(8).
Then, specify the maximum total number of partitions in case of expanding area by adding file data partitions in the "-o maxvol" of sfcmkfs(8) and execute the command again.
