| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.4 Command messages for File System Common Management |
The specified configuration is not the same as the configuration of the previously created file system.
When specifying the -o force option, specify the same configuration as that of the previously created file system and re-execute the command.
An overflow occurred because the value value specified for an option was too large.
Specify a correct value within the range allowed for each option, and re-execute the command.
The nonnumeric character string string was specified for an option parameter for which a numeric value must be specified.
Specify a correct parameter value.
A failure occurred because all communication port numbers have been used.
Add a new communication port number for sfcfs to /etc/services.
Connecting to the cluster control mechanism failed.
Make sure that the cluster control mechanism is operating using the ps command, and re-execute the command.
Specified special was not found.
Check whether the specified special file name is correct, and re-execute the command.
The specified block special file special could not be found.
Specify the name of a special file that can be shared by the specified hosts, and re-execute the command.
Opening the file filename failed.
Check whether the file filename exists, and re-execute the command.
The file data area is not sufficient in size, and therefore, a file system cannot be created.
Review parameters so that a sufficiently large file data area can be reserved.
Opening the special file filename failed.
Take action according to the detailed information errmsg.
Updating the file system configuration information failed.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of errmsg.
An illegal option was specified.
Specify a correct option and argument.
Part of the management data of the specified the GFS Shared File System was destroyed.
Restore it with fsck_sfcfs(1M) or delete it properly with sfcadm(1M).
Specified special is not the absolute path name.
Specify the absolute path name for special, and re-execute the command.
The update log area cannot be created because the representative partition is too small.
Check the specified parameter, allocate enough space for the representative partition, and re-execute the command.
The meta-data area cannot be created because the representative partition is too small.
Review the specified parameter, secure sufficient space on the representative partition, and re-execute the command.
Creation of a file system stops because the meta-data area is too small for managing the specified data area and file.
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.
Communication for the host specified for node has not been enabled.
When communication for the host has been enabled, re-execute the command.
The user executing this command is not a super-user.
Re-execute the command as a super-user.
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.
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(1M) and sfcinfo(1M).
The number of specified sharing hosts exceeds the maximum num for the GFS Shared File System.
Specify no more than num hosts that will share the file system.
No corresponding file system exists while the -o force option was specified.
Specify the same configuration as the file system configuration previously created the -o force option should be set, and re-execute the command.
The number limit of registrable the GFS Shared File Systems was exceeded, and any more file system cannot be added.
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(1M) and sfcinfo(1M).
The specified host name indicated by string has already been specified.
Specify a unique host name for the -o node option.
Mount state acquisition of a special file went wrong.
Please perform management according to the detailed information errmsg.
Obtaining the status of the special file special failed.
Take action according to detailed information indicated by errmsg. For details, see the description of fstat(2).
Obtaining the device size failed.
Take action according to the detailed information errmsg.
lseek(2) could not be executed for special.
Take action according to detailed information indicated by errmsg. For details, see the description of lseek(2).
Memory could not be allocated.
Wait for the termination of another process or increase the swap space according to the detailed information errmsg.
The specified special device special has been used in another GFS Shared File System.
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.
The number limit of registrable GFS Shared File Systems was exceeded, and any other file system cannot be added in filetable.
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(1M) and sfcinfo(1M).
The specified partition indicated by special cannot be changed because the file system is mounted.
Unmount the file system and re-execute the command specifying -o force, or delete the file system with sfcadm(1M) and re-execute the command.
The special device special is not a GFS Shared File System device while the -m option was specified.
Specify a special file created already as a GFS Shared File System, and re-execute the command.
Specified special is not a special device file.
Specify a special file.
read(2) for special failed.
Take action according to detailed information indicated by errmsg. For details, see the description of read(2).
The write(2) operation for special failed.
Take action according to detailed information indicated by errmsg. For details, see the description of write(2).
An error was detected in the internal processing.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
The size of the partition of special has exceeded 1 terabytes.
Reduce the size of special or specify another partition when it is exceeding the maximum partition size, and re-execute the command.
An internal error was detected in the process of newly adding a file system.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
Memory allocation failed.
Wait for the termination of another process or increase the swap space.
Obtaining the file system configuration information failed.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
An internal error was detected in the process of newly adding a file system.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
Obtaining the lock in the file system failed.
Re-execute the command after some interval because another process may currently retain the lock.
Releasing the lock in the file system failed.
Re-execute the command after the mkfs_sfcfs termination releases the lock.
Obtaining Fsid for newly adding a file system failed.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
Obtaining the lock in the domain failed.
Re-execute the command after some interval because another process may currently retain the lock.
Specified special has been used for the file system management.
Specified special is not available because it is in use for the file system management.
Specify another special file to execute the command.
An internal error was detected in the process of newly adding a file system.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
Obtaining the file system configuration information of fsidnumber failed.
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.
special is not the representative partition.
Specify the representative partition of the file system created already.
An error was detected in the internal processing.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
An error was detected in the internal processing with the cluster control mechanism.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
The specified special file is not found.
Check whether the special file exists on any node of the file system.
Securing the file data area failed because the size of the partition special is small.
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.
Obtaining the FsRM management information failed.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
Acquisition of host information of the specified node failed.
Possible causes:
Execute mkfs_sfcfs(1M) again after correcting the cause of the failure according to the following procedures.
# /usr/bin/ps -e | /usr/bin/grep sfcfrmd <Enter> 1629 ? 0:28 sfcfrmd # echo $? <Enter> 0 |
If grep(1)'s return code is 0, sfcfrmd daemon is running.
For details of ps(1) and grep(1), see the "Solaris X Reference Manual Collection".
WARNING: sfcfsrm:5001: Starting the sfcfrmd daemon was suspended because quorum does not exist |
If the message is not output, execute sfcfrmstart(1M) command.
Registration to the file system management information failed.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
An unexpected error was detected in the internal processing.
Collect the diagnostic data with fjsnap, and contact your local Customer Support submitting it along with text of the error message displayed.
The number of partitions specified exceeds the upper limit count specified with the maxvol option.
Increase the value of the maxvol option or decrease the number of partitions configuring the file system by grouping the partitions.
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.
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.
The total partition size exceeds the maximum file system size of 1 terabyte, so a file system cannot be created.
The total partition size (file data partition with -o data and representative partition with operand) must be less than 1 terabyte.
The configuration of the specified partition is different than that of the current partition, so a file system cannot be recreated.
Check the configuration of the current partition using the "mkfs -F sfcfs -m" command. To make the configuration of the specified partition same as that of the displayed current partition by executing mkfs_sfcfs(1M) with the "-o data" option and correct operand.
The specified partition special is being mounted, so it cannot be changed.
Unmount the file system and delete it by executing -o force or sfcadm(1M).
The command cannot be executed in the non-global zone.
For Solaris 10 OS, GFS is allowed to be operated in the global zone only.
Collection of the zone setup information failed.
Check the system then wait until the other process is done, or expand the swap area or memory. Execute the command again.
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.
If there is a problem, specify a correct parameter value, and re-execute the command.
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.
If there is a problem, specify a correct parameter value, and re-execute the command.
The value value specified for the metasz option is outside the valid range. The file system is created using a calculated size.
If there is a problem, specify a correct parameter value, and re-execute the command.
The value value specified for the mfree option is outside the valid range. The file system is created using the default value (10%).
If there is a problem, specify a correct parameter value, and re-execute the command.
The value value specified for the nblkpext option is outside the valid range. The file system is created using the default value (1).
If there is a problem, specify a correct parameter value, and re-execute the command.
The value value specified for the nbpi option is outside the valid range. The file system is created using the default value (8192).
If there is a problem, specify a correct parameter value, and re-execute the command.
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.
When this action comes to an issue, specify a proper parameter value and re-execute the command.
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.
When this action comes to an issue, specify a proper parameter value and re-execute the command.
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.
When this action comes to an issue, specify a proper parameter value and re-execute the command.
An invalid value was specified for dataopt, so the default value n will be specified.
File data area is included in the representative partition of the file system. No corrective action should be taken if this configuration is used. If you want to detach the file data area from the representative partition, delete the file system using sfcadm(1M). Then, specify dataopt=y for mkfs_sfcfs(1M) and execute the command again.
An invalid value was specified for the maxdsz option, so the default value will be specified.
The meta-data area size and update log area size of the 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 additional file data partitions are added to the file system in the future, delete the file system using sfcadm(1M). Then, calculate and specify the maximum total size of the file data area for -o maxdsz of mkfs_sfcfs(1M) and execute the command again.
The value of the maxvol option is out of the valid range, so the default value 16 will be used to create a file system.
The maximum number of partitions of the file system is 16. No corrective action should be taken if this configuration is used. If the number of partitions is more than 16, delete the file system using sfcadm(1M). Then, specify the maximum total number of the partitions for -o maxvol of mkfs_sfcfs(1M) and execute the command again.
|
Contents
Index
|