| PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment) |
|
Contents
Index
|
| Appendix E List of Messages | > E.5 Management Command messages Specific to GFS Shared File System |
Memory could not be allocated. Memory of system is insufficient.
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.
This operation cannot be executed in the state of restoration.
Issue sfcproxybreak(1M) to break the relationship after copy processing is completed so that backup can be executed again. Then later, if necessary, set up the relationship again.
The error occurred during copy processing and the copy went wrong.
Respond according to "24.7.12 Actions following an error" in this manual.
The contents of a management partition are inaccurate.
Contact local Customer Support.
Cannot get the lock for file system. Other command or daemon is operating with lock.
Please wait to complete operating the command or daemon of a GFS Shard file system in all nodes, and re-execute again.
cmd that is called from cmdname of high speed backup function failed.
Check the message of cmd, and operate cmd normally.
After the lock of the renewal operation of a file system, although instant copy processing or separation processing was performed, the lock was canceled in the meantime. Backup may not be created correctly.
Contact local Customer Support.
Even if it has mounted by other nodes with the file system for operation, a command execution node is in a unmount state. Since it was in the state that cannot lock updating operation of a file system, execution of a command went wrong.
At sfcproxyjoin, sfcproxyop backup, sfcproxy part, and sfcproxybreak, a unmount state and a command execution node needs to be in a mount state in all the nodes of a file system. Please check the state of a file system.
The specified device is not a character special file.
Please improve the executed command and the joint state of a backup source and a backup distination.
The command that executed the command that should be executed when a backup source and a backup distination are in a joint state in the state of separation, or should execute it in the case of a separation state was executed in the state of combination.
Please improve the executed command and the joint state of a backup source and a backup distination.
There was no executable command of PRIMECLUSTER Global Disk Services Snapshot. Optional product PRIMECLUSTER Global Disk Services Snapshot is required for this function.
Please put it into the state that PRIMECLUSTER Global Disk Services Snapshot can be used.
cmdname cound not obtained the status of pathname.
Please specify the correct path name, when you specified pathname.
It was going to cancel correlation in the state a backup source or under copy of a backup distination.
In under copy, correlation cannot be canceled. Please wait for completion of a copy, or specify -f option, and perform compulsive release. However, when compulsive release is performed, the volume of a copy distination is data unjust (INVALID.)
The volume of GDS to the file system specified by the representative partition does not exist.
After erasing the volume of GDS, without erasing a file system by sfcadm(1M), it is possible that sfcproxyjoin was performed.
Please delete the file system with sfcadm(1M). Restore the file system from the backup if it is necessary.
The group that does not relate to the file system specified by the argument of -g option is specified by the operand.
Please specify only the group where the file system specified by the argument of -g option exists for an operand.
The volume existed in the group (class.group) of GDS the backup destination. The proxy group must not have any volume.
Please do one of the followings.
It was going to relate between the devices of the class from which GDS differs.
Please improve the partition of a backup distination the specified backup source.
It was going to associate an employment pattern that is different in the file system of the same backup source.
Please improve the executed command.
The partition inaccurate as a backup source or a backup distination was specified. The partition of a different file system as a backiup source or a backup distination was specified.
Please improve the partition composition of a backing up agency or a backup place.
The specified path is inaccurate. This message is outputted when devices other than GDS are specified.
Please check the specified path.
device specified to be the argument of the -g option or an operand is not the thing of a GFS shared file system.
Please delete t device, or set the character special file of the representative partition of a correct GFS shared file system to the argument of the operand or -g option.
The group (class.group) including the partition device of the file system specified by the argument of -g option is not specified by the operand.
Please correct the representative partition name of -g option or the pair of the group of the operand.
A setup of the MDS node of the file system device1 of a backup source and the file system device2 of a backup distination and AC node was not in agreement.
Please improve a setup of a backup source and the MDS node of a backup distination, and AC node. When the file system of a backup distination is unnecessary, please delete the file system of a backup distination and re-perform.
The specified number of groups exceeded upper bound n.
Please specify only the group where the file system specified by the argument of -g option exists for an operand.
The same device was specified two or more times. The specification error of an operand can be considered.
Please specify a backup distination by the operand the right backup source.
The size of the partition device1 of a backup source and the partition device2 of the backup distination corresponding to it is not equal.
Please improve the partition composition of a backing up agency or a backup place.
The volume of the group cannot be made the backup corresponding to the volume that exists in the group (class.group) in the backup source because the volume name becomes long.
Please improve the partition composition of a backup source or a backup distination.
The specified file system is a file system of two or more partition composition. It cannot be specified as the candidate for backup.
Please remake a file system in single partition composition.
The file system (device) that the mount is being done by the group in the backup source exists.
None.
Please examine the re-creation of the volume of GDS so that only the file system to be backed up may exist in the group.
Although a part of correlation of GDS was performed, before correlation of all partitions was performed, the error occurred. Correlation will be set up partially.
Please execute the shown command after completion of copy processing, and cancel the correlation by the side of GDS. Please specify and perform -e force at the last of the sdxproxy break command to cancel correlation, without waiting for completion of copy processing. However, when -e force is attached and performed, the volume of a copy place may be data unjust (INVALID.) It is necessary to investigate the cause used as the error after release of correlation.
It is not in the state that can be mounted. It is already mounted from other nodes, or the node down occurred during mount. It is necessary to investigate the cause used as the error after release of correlation.
It cannot mount, when already mounted from other nodes. When a node down occurs during mount, please mount after restoration of a file system by fsck_sfcfs(1M).
Although a part of inclusion processing of GDS or separation processing was performed, before processing of all partitions was performed, the error occurred. The joint state and the separation state will be intermingled.
Please cancel correlation by sfcproxybreak(1M). It is necessary to investigate the cause used as the error after release of correlation.
All the nodes of the file system of a backing up agency (restoration place) were not in the unmount state.
Since all the nodes of the file system of a backing up agency (restoration place) are changed into a unmount state, please re-perform.
rel_name entered in the state restoration.
None.
Issue sfcproxybreak(1M) to break the relationship after copy processing is completed so that backup can be executed again. Then later, if necessary, set up the relationship again.
|
Contents
Index
|