E.4.3 mkfs_sfcfs command

PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

Contents Index

Appendix E List of Messages

> E.4 Command messages for File System Common Management

E.4.3 mkfs_sfcfs command

E.4.3.1 mkfs_sfcfs: ERROR: {Node|Mds|Partiton|Meta|Log|Data} is not same

[Explanation]

The specified configuration is not the same as the configuration of the previously created file system.

[Action]

When specifying the -o force option, specify the same configuration as that of the previously created file system and re-execute the command.

E.4.3.2 mkfs_sfcfs: ERROR: Argument out of range: value

[Explanation]

The value (value) specified for an option was too large.

[Action]

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

E.4.3.3 mkfs_sfcfs: 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.

[Action]

Specify a correct parameter value.

E.4.3.4 mkfs_sfcfs: 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 mkfs_sfcfs(1M) again.

E.4.3.5 mkfs_sfcfs: ERROR: Cannot find {any|free} port of sfcfs in file

[Explanation]

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

[Action]

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

E.4.3.6 mkfs_sfcfs: can't find hostname as hostname

[Explanation]

Command argument hostname is wrong, or a file system recovery manager is not active on hostname.

[Action]

Check command argument hostname. If a file system recovery manager is not active on hostname, execute sfcfrmstart(1M) command.

E.4.3.7 mkfs_sfcfs: ERROR: Cannot look up node

[Explanation]

The specified valid node (node) could not be found in the domain in which mkfs_sfcfs(1M) was executed.

[Action]

Specify a correct host name for node, and re-execute the command.

E.4.3.8 mkfs_sfcfs: ERROR: Cannot look up raw_device_file in node

[Explanation]

The specified raw device file raw_device_file could not be found.

[Action]

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

E.4.3.9 mkfs_sfcfs: ERROR: Cannot open file: errmsg

[Explanation]

File file could not be opened.

[Action]

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

E.4.3.10 mkfs_sfcfs: 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.

[Action]

Review parameters so that a sufficiently large file data area can be reserved.

E.4.3.11 mkfs_sfcfs: ERROR: File system is corrupted, run fsck manually

[Explanation]

The file system cannot be created because it is not terminated normally in the middle of partition addition.

[Action]

Repair the file system using fsck_sfcfs(1M). Complete partition addition using sfcadd(1M), then re-execute mkfs_sfcfs(1M).

E.4.3.12 mkfs_sfcfs: ERROR: Illegal host in the specified file system.

[Explanation]

The host that executed mkfs_sfcfs(1M) does not belong to the host group of the specified file system.

[Action]

Execute mkfs_sfcfs(1M) using the host belonging to the host group name of the specified file system.

E.4.3.13 mkfs_sfcfs: ERROR: Illegal option: option

[Explanation]

An illegal option was specified.

[Action]

Specify a correct option and argument.

E.4.3.14 mkfs_sfcfs: ERROR: Invalid magic word 0xmagic

[Explanation]

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

[Action]

Restore the management data using fsck_sfcfs(1M), or delete it correctly using sfcadm(1M).

E.4.3.15 mkfs_sfcfs: ERROR: LOG partition small, need over size mega bytes

[Explanation]

A file system cannot be created because the update log partition is too small.

[Action]

Check the parameter, and allocate size megabytes or more for the update log partition.

E.4.3.16 mkfs_sfcfs: 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.

[Action]

Check the specified parameter, allocate enough space for the representative partition, and re-execute the command.

E.4.3.17 mkfs_sfcfs: ERROR: Master partition is small, meta area not enough

[Explanation]

The meta-data area cannot be created because the representative partition is too small.

[Action]

Check the specified parameter, allocate enough space for the representative partition, and re-execute the command.

E.4.3.18 mkfs_sfcfs: 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.

[Action]

Specify a larger value for the metasz parameter to increase the size of the meta-data area. Alternatively, check the data partition and nbpi and other parameters, and reduce the size of the meta-data area.

E.4.3.19 mkfs_sfcfs: ERROR: No response from node

[Explanation]

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

[Action]

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

E.4.3.20 mkfs_sfcfs: ERROR: Not super user

[Explanation]

The user executing this command is not a super user.

[Action]

Re-execute the command as a super user.

E.4.3.21 mkfs_sfcfs: 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.

[Action]

If possible, delete an unnecessary GFS Shared File System, and re-execute the command. For details of how to delete a file system, see the description of sfcadm(1M) and sfcinfo(1M).

Extend the capacity of an existing GFS Shared File System to correct the error. For details, see the description of sfcadd(1M).

E.4.3.22 mkfs_sfcfs: ERROR: Number of hostname is over num

[Explanation]

The number of specified sharing hosts exceeds the maximum num for GFS Shared File System.

[Action]

Specify no more than four hosts that will share the file system.

E.4.3.23 mkfs_sfcfs: ERROR: Number of mdsnode is over num

[Explanation]

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

[Action]

Limit the MDS operational information to num.

E.4.3.24 mkfs_sfcfs: ERROR: Number of partition is over count in maxvol

[Explanation]

The number of specified partitions exceeded the upper limit count specified for the maxvol option.

[Action]

Specify a larger value for the maxvol option, or decrease the number of partitions configuring the file system by combining partitions into a larger partition.

E.4.3.25 mkfs_sfcfs: ERROR: Same device is specified more than once

[Explanation]

The specified partition has already been specified.

[Action]

Change the specification so that a partition is specified only as a representative, update log, or data partition.

E.4.3.26 mkfs_sfcfs: ERROR: Same hostname string is specified more than once

[Explanation]

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

[Action]

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

E.4.3.27 mkfs_sfcfs: ERROR: failed to check service is stopped : errmsg

[Explanation]

Mount state acquisition of a special file went wrong.

[Action]

Please perform management according to the detailed information errmsg.

E.4.3.28 mkfs_sfcfs: ERROR: filesystem size is over size terabytes.

[Explanation]

Because the total size of the specified partition is maximum capacity size or more of file system, file system cannot be created.

[Action]

Decrease the number of the specified partitions, or review the size of the partitions specified for total size of the partitions to become less than size.

E.4.3.29 mkfs_sfcfs: ERROR: fstat(2) error special: errmsg

[Explanation]

The status of a special file could not be obtained.

[Action]

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

E.4.3.30 mkfs_sfcfs: ERROR: ioctl(2) {DKIOCINFO|DKIOCGVTOC} error: errmsg

[Explanation]

Device information could not be obtained.

[Action]

Check the system environment to see whether the specified special file is ready to use, and re-execute the command.

E.4.3.31 mkfs_sfcfs: ERROR: lseek(2) error raw_device_file: errmsg

[Explanation]

lseek(2) could not be executed for raw_device_file.

[Action]

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

E.4.3.32 mkfs_sfcfs: ERROR: malloc(3C) error: errmsg

[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.4.3.33 mkfs_sfcfs: ERROR: raw_device_file is already used

[Explanation]

The specified character special device is used with the other GFS Shared File System.

[Action]

Re-execute the command after taking one of the following actions:

Use an unused character 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.

E.4.3.34 mkfs_sfcfs: ERROR: raw_device_file is already used as transit device.

[Explanation]

Since it is in other file systems in the middle of additional, specified partition raw_device_file cannot be used.

[Action]

By sfcinfo(1M), check that the partition to specify is not in the middle of additional, and re-perform sfcadd(1M).

E.4.3.35 mkfs_sfcfs: 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.

[Action]

Unmount the file system, delete the file system using sfcadm(1M) and , and re-execute the command.

E.4.3.36 mkfs_sfcfs: ERROR: raw_device_file is not a sfcfs file system

[Explanation]

The specified character special device indicated by raw_device_file is not the GFS Shared File System.

[Action]

Specify the character special file of the GFS Shared File System.

Execute the command without specifying the -o force option, or correct the /etc/vfstab setting.

E.4.3.37 mkfs_sfcfs: ERROR: raw_device_file is not special device, can't mkfs

[Explanation]

The specified raw_device_file is not a character special file.

[Action]

Specify a character special file.

E.4.3.38 mkfs_sfcfs: ERROR: read(2) error at raw_device_file: errmsg

[Explanation]

read(2) for raw_device_file failed.

[Action]

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

E.4.3.39 mkfs_sfcfs: ERROR: write(2) error at special: errmsg

[Explanation]

I/O for special failed.

[Action]

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

E.4.3.40 reset to time: bogus optimization preference reset to opt

[Explanation]

The value opt specified for the opt option is illegal. The file system is created using the default value indicated by time.

[Action]

If there is a problem when opt option is time, delete the file system by sfcadm(1M) command and set opt = s and then re-execute the command.

E.4.3.41 value: bogus logsz reset to system set value

[Explanation]

The value value specified for the logsz option is outside the valid range. The file system is created using a calculated size.