| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System) |
|
Contents
Index
|
| Appendix A List of Messages | > A.5 The GFS Shared File System Specific Management Commands' Messages |
Execution was attempted with other than super-user permission.
Retry execution with super-user permission.
Memory acquisition failed. System memory is insufficient.
Check the system status then wait for the other process to be completed or expand the swap area or actual memory.
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 mkfs_sfcfs(1M). The upper limit cannot be changed.
Specify the upper limit or less and execute the command again.
The same partitions exists in the partition specified.
Check if the specified partition is correct.
The file system monitoring mechanism is not operating.
Confirming the state of sfcfrmd daemon by using the likes of the ps(1) command. If it does not, activate the file system monitoring facility by executing the sfcfrmstart(1M).
An error is detected.
Check if the DNS settings are correct. If they are, collect troubleshooting information with fjsnap the contact your local customer support engineers.
Acquisition of the file system lock failed. The other command has acquired the lock.
Wait until the management command of the GFS Shared File System to be completed on all the cluster nodes then execute the command again.
Reading of the management partition failed.
Check if the management partition is set using the sfcsetup(1M) command.
If it is not, set the management partition using sfcsetup(1M). If it is, collect troubleshooting information with fjsnap the contact your local customer support engineers.
The special file special cannot be used because it is being used as a management partition.
Specify the other partition and execute the command again.
Acquisition of the file configuration failed.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
special does not exist in the management partition.
Specify a character special file name of the existing representative partition of the GFS Shared File System for special.
The identifier number num of the specified file system is not registered.
Collect a file output with fjsnap for troubleshooting information then contact your customer support engineers.
The special file special specified is nonexistent.
Check if the special file special exists.
The partition special is already being used for the GFS Shared File System.
Specify a partition that is not used for the GFS Shared File System.
The special file special is different is shared by a different representative partition and node.
Specify a correct representative partition and node that are consistent.
The special file special is being mounted, so the sfcadd(1M) cannot be executed.
Unmount the special file special then execute the command again.
The special file special is being mounted on the other node, so the sfcadd(1M) cannot be executed.
Unmount the special file special then execute the command again.
Opening of the special file special failed.
Check if the special file special is correct.
Acquisition of the special file special failed.
Check if the special file special is correct.
The specified file (special) is not a character special file.
Specify a character special file.
The additional partition special is described in /etc/vfstab.
Check the "/etc/vfstab" file. If the partition special is added, delete special from /etc/vfstab.
Opening of /etc/mnttab failed.
Recover /etc/mnttab then execute the command again.
Opening of /etc/vfstab failed.
Check if /etc/vfstab exists. If it does not, restore the file from backed up data, or define the file again according to "11.2.3 Setting vfstab".
There is an invalid line in /etc/vfstab.
Modify the /etc/vfstab file.
The size of the partition special exceeds the maximum file system size.
Set the size of the partition special not to exceed the maximum file system size, or specify the other partition.
Acquisition of the device special failed.
Check if a disk I/O error is output then take corrective action according to the error message.
Special is not a representative partition.
Specify a representative partition for operand.
Reading of the special super block failed.
Recover the file system using fsck_sfcfs(1M). If the message "special is clean" is output, recover the file system by executing fsck_sfcfs(1M) with the options -o f,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.
special is not of the GFS Shared File System.
Recreate the file system then restore the backed up data.
Writing of the special super block failed.
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 fsck_sfcfs(1M) with the options -o f,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.
special is not of the GFS Shared File System.
Specify a GDS volume.
If the specified partition is added, the file system size will exceed the maximum file system size, so the partition cannot be added.
Specify a partition where the file system size will not exceed the maximum file system size.
Writing of the special partition configuration failed.
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 fsck_sfcfs(1M) with the options -o f,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.
Recovering of the special super block failed.
Copy the super block of the representative partition to the partition that configures the file system by executing sfcadm(1M). Then, recover the file system by executing fsck_sfcfs(1M) 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.
special and the device number of special are the same.
Check if the specified partition is correct.
Updating the meta-data area failed.
Recover the file system using fsck_sfcfs(1M). If the message "special is clean" is output, recover the file system by executing fsck_sfcfs(1M) with the options -o f,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.
Recovering the meta-data area failed.
Recreate the file system then restore the backed up data.
sfcadd(1M) cannot be executed because the state of the file system of the partition special was not stopped properly.
Recover the file system using fsck_sfcfs(1M). 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.
Recovering of the special partition configuration failed.
Copy configuration information of the representative partition to the partition that configures the file system by executing sfcadm(1M). Then, recover the file system by executing fsck_sfcfs(1M) with the options -o f,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.
Reading of special partition configuration information failed.
Recover the file system by executing fsck_sfcfs(1M) with the options -o f,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.
Reading of the /etc/mnttab file failed.
Recover the /etc/mnttab then execute the command again.
The sfcfrmd daemon of the node that shares the representative partition has not been activated.
Check if the sfcfrmd daemon exists by executing the ps(1) command on all the nodes that share the representative partition. The nodes can be checked with sfcinfo(1M).
If the nodes are stopped, start them. If the sfcfrmd daemon does not exist, activate the daemon using sfcfrmstart(1M) on the node. If it does, collect troubleshooting information using fjsnap then contact your customer support engineers.
Reading of the setup file /var/opt/FJSVgfs/sfcfsrm.conf failed.
Recover the system in the event of a disk failure. If a disk failure does not occur, collect troubleshooting information using fjsnap then contact your customer support engineers.
The command is executed on the node that does not share the file system.
Execute the command on the node that shares the file system.
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.
|
Contents
Index
|