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

Appendix A List of Messages> A.3 GFS Shared File System Exclusive Management Command Messages

A.3.3 sfcmkfs command


 

sfcmkfs:ERROR: {Node | Mds | Partition } is not same

[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.


 

sfcmkfs:ERROR: Argument out of range: value

[Explanation]

An overflow occurred because the value value specified for an option was too large.

[Response]

Specify a correct value within the range allowed for each option, and re-execute the command.


 

sfcmkfs:ERROR: Bad numeric arg: "string"

[Explanation]

The nonnumeric character string string was specified for an option parameter for which a numeric value must be specified.

[Response]

Specify a correct parameter value.


 

sfcmkfs:ERROR: Cannot find {any | free} port of sfcfs in file

[Explanation]

A failure occurred because all communication port numbers have been used.

[Response]

Add a new communication port number for sfcfs to /etc/services.


 

sfcmkfs:ERROR: Cannot connect to cluster

sfcmkfs:ERROR: can not connect to CLUSTER SYSTEM

[Explanation]

Connecting to the cluster control mechanism failed.

[Response]

Make sure that the cluster control mechanism is operating using the ps command, and re-execute the command.


 

sfcmkfs:ERROR: Cannot look up raw_device_file

[Explanation]

Specified raw_device_file was not found.

[Response]

Check whether the specified special file name is correct, and re-execute the command.


 

sfcmkfs:ERROR: Cannot look up raw_device_file in node

[Explanation]

The specified raw device file raw_device_file could not be found.

[Response]

Specify the name of a special file that can be shared by the specified hosts, and re-execute the command.


 

sfcmkfs:ERROR: Cannot open file : filename

[Explanation]

Opening the file filename failed.

[Response]

Check whether the file filename exists, and re-execute the command.


 

sfcmkfs:ERROR: Data area is too small, can't mkfs

[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.


 

sfcmkfs:ERROR: can not open special : filename(errmsg)

[Explanation]

Opening the special file filename failed.

[Response]

Take action according to the detailed information errmsg.


 

sfcmkfs:ERROR: sfcfs_synctab : Cannot write to file system configuration information : errmsg

[Explanation]

Updating the file system configuration information failed.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of errmsg.


 

sfcmkfs:ERROR: Illegal option: option

[Explanation]

An illegal option was specified.

[Response]

Specify a correct option and argument.


 

sfcmkfs:ERROR: Invalid magic word 0xmagic

[Explanation]

Part of the management data of the specified GFS Shared File System was destroyed.

[Response]

Restore it with sfcfsck(8) or delete it properly with sfcadm(8).


 

sfcmkfs:ERROR: raw_device_name is not full path name

[Explanation]

Specified raw_device_name is not the absolute path name.

[Response]

Specify the absolute path name for raw_device_name, and re-execute the command.


 

sfcmkfs:ERROR: Master partition is small, log area space not enough

[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.


 

sfcmkfs:ERROR: Master partition is small, meta area not enough

[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.


 

sfcmkfs:ERROR: Metasz small, can't mkfs

[Explanation]

Creation of a file system stops because the meta-data area is too small for managing the specified data area and file.

[Response]

Specify a larger value for a metasz parameter in order to increase the size of the meta-data area, or review such a parameter as nbpi for less meta-data space.


 

sfcmkfs:ERROR: No Response from node

[Explanation]

Communication for the host specified for node has not been enabled.

[Response]

When communication for the host has been enabled, re-execute the command.


 

sfcmkfs:ERROR: Not super-user

[Explanation]

The user executing this command is not a super-user.

[Response]

Re-execute the command as a super-user.


 

sfcmkfs:ERROR: Number of file system is over count

[Explanation]

The new GFS Shared File System could not be added because the maximum number of file systems in the same domain indicated by count was exceeded.

[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).


 

sfcmkfs:ERROR: Number of hostname is over num

[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.


 

sfcmkfs:ERROR: Number of mdsnode is over num

[Explanation]

The MDS operational information exceeds the limit of num that can be specified.

[Response]

Limit the MDS operational information to num.


 

sfcmkfs:ERROR: not entry 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.


 

sfcmkfs:ERROR: No more add filesystem

[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).


 

sfcmkfs:ERROR: Same hostname string is specified more than once

[Explanation]

The specified host name indicated by string has already been specified.

[Response]

Specify a unique host name for the -o node option.


 

sfcmkfs:ERROR: failed to check service is stopped : errmsg

[Explanation]

Mount state acquisition of a special file went wrong.

[Response]

Please perform management according to the detailed information errmsg.


 

sfcmkfs:ERROR: fstat(2) failed raw_device_file : errmsg

[Explanation]

Obtaining the status of the special file raw_device_file failed.

[Response]

Take action according to detailed information indicated by errmsg. For details, see the description of fstat(2).


 

sfcmkfs:ERROR: ioctl(2) { BLKGETSIZE } error: errmsg

[Explanation]

Obtaining the device size failed.

[Response]

Take action according to the detailed information errmsg.


 

sfcmkfs:ERROR: lseek(2) failed raw_device_file: errmsg

[Explanation]

lseek(2) could not be executed for raw_device_file.

[Response]

Take action according to detailed information indicated by errmsg. For details, see the description of lseek(2).


 

sfcmkfs:ERROR: malloc(3C) failed: errmsg

[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.


 

sfcmkfs:ERROR: raw_device_file is already used

[Explanation]

The specified special device raw_device_file 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.


 

sfcmkfs:ERROR: Cannot add data, file filetable

[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).


 

sfcmkfs:ERROR: raw_device_file is mounted, can't mkfs

[Explanation]

The specified partition indicated by raw_device_file 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.


 

sfcmkfs:ERROR: special is not a sfcfs file system

[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.


 

sfcmkfs:ERROR: raw_device_file is not special device, can't mkfs

[Explanation]

Specified raw_device_file is not a special device file.

[Response]

Specify a special file.


 

sfcmkfs:ERROR: read(2) error at raw_device_file: errmsg

[Explanation]

read(2) for raw_device_file failed.

[Response]

Take action according to detailed information indicated by errmsg. For details, see the description of read(2).


 

sfcmkfs:ERROR: write(2) error at raw_device_file: errmsg

[Explanation]

The write(2) operation for raw_device_file failed.

[Response]

Take action according to detailed information indicated by errmsg. For details, see the description of write(2).


 

sfcmkfs:ERROR: Fsid out of range

[Explanation]

An error was detected in the internal processing.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: raw_device_name partition size is over 1TB

[Explanation]

The size of the partition of raw_device_name has exceeded 1 TB.

[Response]

Reduce the size of raw_device_name or specify another partition when it is exceeding the maximum partition size, and re-execute the command.


 

sfcmkfs:ERROR: fsid bad entry

[Explanation]

An internal error was detected in the process of newly adding a file system.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: Not enough memory

[Explanation]

Memory allocation failed.

[Response]

Wait for the termination of another process or increase the swap space.


 

sfcmkfs:ERROR: Not read file system configuration information

[Explanation]

Obtaining the file system configuration information failed.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support.


 

sfcmkfs:ERROR: Fsid already in use

[Explanation]

An internal error was detected in the process of newly adding a file system.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: can not sfcfs_lock

[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.


 

sfcmkfs:ERROR: can not unlock

[Explanation]

Releasing the lock in the file system failed.

[Response]

Re-execute the command after the sfcmkfs termination releases the lock.


 

sfcmkfs:ERROR: can not get fsid

[Explanation]

Obtaining Fsid for newly adding a file system failed.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: can not configlock

[Explanation]

Obtaining the lock in the domain failed.

[Response]

Re-execute the command after some interval because another process may currently retain the lock.


 

sfcmkfs:ERROR: raw_device_name is already used for the management partition.

[Explanation]

Specified raw_device_name has been used for the file system management.

[Response]

Specified raw_device_name is not available because it is in use for the file system management.

Specify another special file to execute the command.


 

sfcmkfs:ERROR: can not acquire fsid

[Explanation]

An internal error was detected in the process of newly adding a file system.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: no entry fsid = fsidnumber

[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.


 

sfcmkfs:ERROR: raw_device_name is not Master Partition

[Explanation]

raw_device_name is not the representative partition.

[Response]

Specify the representative partition of the file system created already.


 

sfcmkfs:ERROR: Global Memory Broken

[Explanation]

An error was detected in the internal processing.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: cluster error

[Explanation]

An error was detected in the internal processing with the cluster control mechanism.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: The specified device does not exist

[Explanation]

The specified special file is not found.

[Response]

Check whether the special file exists on any node of the file system.


 

sfcmkfs:ERROR: partition [raw_device_name] is small, can't acquire data area

[Explanation]

Securing the file data area failed because the size of the partition raw_device_name is small.

[Response]

Specify the bigger partition for raw_device_name or adjust such parameters as metasz and logsz for smaller size in order to secure the file data area, and re-execute the command.


 

sfcmkfs:ERROR: cannot read the FsRM configuration file: errno = value

[Explanation]

Obtaining the FsRM management information failed.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: Can not get host information

[Explanation]

Obtaining the file system management information failed.

[Response]

Check whether the specified host name is correct.


 

sfcmkfs:ERROR: cannot update the management partition: errno = value

[Explanation]

Registration to the file system management information failed.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:ERROR: Unknown error : value

[Explanation]

An unexpected error was detected in the internal processing.

[Response]

Collect the diagnostic data with pclsnap, and contact your local Customer Support submitting it along with text of the error message displayed.


 

sfcmkfs:WARNING: value : bogus logsz reset to system set value

[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.


 

sfcmkfs:WARNING: value : bogus maxnode reset to 16

[Explanation]

The parameter value, value, specified by the maxnode option lies outside the valid range, and the default value 16 is applied to create the file system.

[Response]

If there is a problem, specify a correct parameter value, and re-execute the command.


 

sfcmkfs:WARNING: value : bogus metasz reset

[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.


 

sfcmkfs:WARNING: value : bogus mminfree reset to 10%

[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.


 

sfcmkfs:WARNING: value : bogus nblkpext reset to 1

[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.


 

sfcmkfs:WARNING: value : bogus nbpi reset to 8192

[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.


 

sfcmkfs:WARNING: value : log size of partition is over : Retry Auto size

[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.


 

sfcmkfs:WARNING: value : meta size of partition is over : Retry Auto size

[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.


 

sfcmkfs:WARNING: value : bogus free reset to 10%

[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.


Contents Index PreviousNext

All Rights Reserved, Copyright(C) FUJITSU LIMITED 2004