| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.2 (Linux) |
|
Contents
|
| Appendix E GDS Messages | > E.4 Command Messages |
The size of disk is too small and may not function as a spare disk.
Specify a larger disk, and execute the command again.
A write error occurred in physical disk device.
If device is a write-locked disk that is connected to a switch group, no action is required. Otherwise, remove device from the class and check the status of device.
Free blocks on group was reduced.
You may not be able to create a volume with sufficient capacity.
Execute commands as needed and attempt recovery.
You must connect another disk to group.
Connect another disk.
Synchronization copying did not complete successfully.
Disk failure may have occurred. Identify the cause by referring to GDS log message and syslog message.
Synchronization copying was canceled before completion.
Check the status of the object object. If the copying is in progress, there is no need to work around. If it is not in progress, re-execute the copying where it is necessary. For details, see "Command Reference."
There is no valid spare disk in group.
Define a spare disk as needed.
Slice object.volume could not be attached since it is in status status.
Check the slice status and cancel status status as needed.
There was no need to resize the volume volume.
No particular resolution required.
Special file for slice disk.volume could not be found.
No particular resolution required.
node is in STOP status.
No particular resolution required. However, promptly activating the node is recommended.
node is in abnormal status.
No particular resolution required. However, promptly recovering the node and activating it normally is recommended.
object is already in status status.
No particular resolution required.
A write error occurred on physical disk device.
If device is a write-locked disk that is connected to a switch group, no action is required. In other situations, have device switchable and check its status.
A write error occurred on physical disk device on node node.
If device is a write-locked disk that is connected to a switch group, no action is required. In other situations, have device switchable and check its status.
There was no need to change object attributes.
No particular resolution required.
Entry in the /etc/fstab file relevant to the physical slice pslice was not updated since fstype is a file system type not supported by the sdxroot command.
Edit the /etc/fstab file or change the file system configuration according to need.
The /etc/fstab file contains an invalid entry. When an entry for a file system, such as / (root), /usr, and /var, essential to system start-up is invalid, it will be impossible to start the system if rebooted.
Refer to a GDS's WARNING message output just before this message and pinpoint the invalid entry in the /etc/fstab file. Be sure to repair the /etc/fstab file and the file system configuration as needed prior to rebooting the system.
Since file system type fstype is not supported, entry in /etc/fstab file for volume could not be updated.
Directly edit /etc/fstab as necessary.
Since EC function will be used for copying, parameter param was ignored.
Since OPC function will be used for copying, parameter param was ignored.
Parameter param was ignored for copying with TimeFinder.
Parameter param was ignored for copying with SRDF.
No copy session exists between the proxy proxy and the master
No special action is required.
|
Contents
|