| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Linux) |
|
Contents
|
| Appendix E GDS Messages | > E.4 Command Messages |
Awaiting response from sdxservd daemon.
class was created.
disk was registered.
/dev/devices*
Physical special files can no longer be accessed.
class was removed.
group was created.
disk was connected to group.
Group lgroup was connected to another group hgroup.
group was removed.
Waiting for synchronization copying to complete.
Synchronization copying completed successfully.
volume was created.
/dev/sfdsk/class/rdsk/volume
/dev/sfdsk/class/dsk/volume
volume was started on node. You can now access via special file.
volume was stopped on node.
volume was removed.
The volume volume was resized.
disk was disconnected from group.
Group lgroup was disconnected from hgroup.
Free blocks on group increased.
disk was removed from class.
/dev/devices*
You can now access to physical special files.
Slice disk.volume was temporarily disconnected from volume.
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Slice disk.volume can now be accessed partly from volume.
Use the special file displayed.
Slice disk.volume cannot be accessed any more.
Slice disk.volume is attached to volume again.
disk is ready for swapping. When using a file unit device supporting active swap, you may remove the physical disk device at this point for swapping. If active swap is not supported, shut down the system and turn off the power before removing the physical disk.
On node node, physical disk device of disk disk is now switchable. If the disk unit supports hot swap, you may simply demount device connected to node and perform swapping. If it does not support hot swap, shot down node and turn off the power, then demount device and perform swapping.
disk restored its original status.
volume was recovered based on disk.
Volume volume was recovered based on lower level group lgroup.
Volume volume in group group has been recovered.
disk disk was recovered.
There is no slice that needs synchronization copying to be started, or resumed in volume.
Synchronization copying of volume has been cancelled.
There is no slice in the process of copying in volume.
Synchronization copying on volume was canceled.
Attribute value of class was updated.
Attribute value of disk was updated.
Attribute value of group was updated.
Attribute value of volume was updated.
Attribute value of slice was updated.
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Slice disk.volume was activated on node.
You may access slice by using the displayed special file.
Slice disk.volume was stopped on node.
You cannot access slice until it is activated again.
Slice disk.volume has become unavailable on remote node node.
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Current node took over slice disk.volume and activated it.
You may access to slice by using the displayed special file.
Modification of parameter related to the copying process of volume is complete.
Modification of configuration parameter is complete.
Proxy proxy has been related and joined to master master.
Proxy volume proxy has been created.
Relationship between master and proxy proxy has been cancelled.
Relationship between master and proxy proxy was forcibly cancelled.
In order to restore data of proxy proxy, volume must be restored with sdxfix(8) command.
/dev/sfdsk/class/rdsk/volume
/dev/sfdsk/class/dsk/volume
Volume was started on node node,*. It can be accessed with the special file.
Proxy proxy was parted from master.
Proxy proxy was immediately parted from master.
Proxy proxy has been rejoined to master master.
Copying from proxy proxy to master master started.
Copying from proxy proxy to master master started. Even if the copying is in process, you may start master volumes and access valid data.
Slice comprising proxy and slice comprising master have been swapped.
A session of the disk unit's copy function that resided between proxy proxy and the master was canceled.
Master master and proxy proxy were related and parted.
Data of proxy proxy was updated with data of master master.
Data of proxy proxy was instantly updated with data of master master.
Local node node obtained master privileges of shared class class.
|
Contents
|