| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
|
Contents
|
| Appendix E GDS Messages | > E.4 Command Messages |
Awaiting response from sdxservd daemon.
class was created.
disk was registered.
/dev/rdsk/devices*
/dev/dsk/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/rdsk/devices*
/dev/dsk/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
The slice disk.volume can now be accessed independently of the 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.
Recovery of the class class from the closed status succeeded.
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.
/etc/vfstab file has been updated.
/kernel/drv/sfdsk.conf file has been updated.
/etc/system file has been updated.
Definition for system disk mirroring is complete.
shutdown -y -g0 -i6
Reboot the system by executing the following command.
shutdown -y -g0 -i6
Canceling definition for system disk mirroring is complete.
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
The slice disk.volume was activated on node.
You may access the 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
The current node node took over the slice disk.volume and activated it.
You may access the 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(1M) command.
/dev/sfdsk/class/rdsk/volume
/dev/sfdsk/class/dsk/volume
The volume volume started on the nodes 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.
details
The file system on the alternative root volume volume will be inspected and repaired with the fsck(1M) command. details is the message for the fsck(1M) command.
The /etc/vfstab file on the alternative root volume volume was updated.
The volume volume is used as a dump device in an alternative boot environment. volume is made available as a dump device when the alternative boot environment is enabled.
The /etc/system file on the alternative root volume volume was updated.
old=old-boot-device ...
new=new-boot-device ...
The boot-device parameter old-boot-device ... was replaced with new-boot-device .... Be sure to take a copy of old-boot-device ... and new-boot-device ... To cancel the switching to the alternative boot environment, execute the following command.
# eeprom boot-device="old-boot-device ..."
Alternatively, execute the following command in the OpenBoot environment.
ok setenv boot-device old-boot-device ...
In general, the number of boot device names for old-boot-device ... and new-boot-device ... corresponds to the number of disks in the current boot environment and the alternative boot environment respectively. However, GDS may not recognize device names depending on some controller types. If that is so, two device names for one boot disk are displayed, but it has no effect on the operation.
The boot environment switching is now defined.
current-boot-device=current-boot-device ...
alternative-boot-device=alternative-boot-device ...
The alternative boot environment is now defined. The boot device names in the current boot environment are current-boot-device ... and those in the alternative boot environment are alternative-boot-device ... Be sure to take a copy of current-boot-device ... and alternative-boot-device ... Executing the following command in the OpenBoot environment can switch to the alternative boot environment.
ok setenv boot-device alternative-boot-device ...
In general, the number of boot device names for current-boot-device ... and alternative-boot-device ... corresponds to the number of disks in the current boot environment and the alternative boot environment respectively. However, GDS may not recognize device names depending on some controller types. If that is so, two device names for one boot disk are displayed, but it has no effect on the operation.
The object configuration of class class was backed up in object table format to configuration file file.
The configuration table was converted successfully. file indicates a configuration file to which the configuration table was output.
Physical disk device retains unremoved disk identification information.
Waiting for restoration of the object configuration of class class.
The class configuration was restored based on configuration file file.
Local node node obtained master privileges of shared class class.
|
Contents
|