INFO: waiting for a response from sdxservd daemon...
Explanation
Awaiting response from sdxservd daemon.
INFO: class: created class
Explanation
class was created.
INFO: disk: created disk
Explanation
disk was registered.
INFO: device: disabled access to physical special files
/dev/rdsk/devices*
/dev/dsk/devices*
Explanation
Physical special files can no longer be accessed.
INFO: class: removed class
Explanation
class was removed.
INFO: group: created group
Explanation
group was created.
INFO: disk: connected disk to group group
Explanation
disk was connected to group.
INFO: lgroup: connected group to another group hgroup
Explanation
Group lgroup was connected to another group hgroup.
INFO: group: removed group
Explanation
group was removed.
INFO: object: waiting for the completion of copying...
Explanation
Waiting for synchronization copying to complete.
INFO: object: copying completed successfully
Explanation
Synchronization copying completed successfully.
INFO: volume: created volume
Explanation
volume was created.
INFO: volume: started volume on node node
/dev/sfdsk/class/rdsk/volume
/dev/sfdsk/class/dsk/volume
Explanation
volume was started on node. You can now access via special file.
INFO: volume: stopped volume on node node
Explanation
volume was stopped on node.
INFO: volume: removed volume
Explanation
volume was removed.
INFO: volume: resized volume
Explanation
The volume volume was resized.
INFO: disk: disconnected disk from group group
Explanation
disk was disconnected from group.
INFO: lgroup: disconnected group from group hgroup
Explanation
Group lgroup was disconnected from hgroup.
INFO: group: free blocks are increased
Explanation
Free blocks on group increased.
INFO: disk: removed disk
Explanation
disk was removed from class.
INFO: device: enabled access to physical special files
/dev/rdsk/devices*
/dev/dsk/devices*
Explanation
You can now access to physical special files.
INFO: disk.volume: temporarily detached slice from volume volume
Explanation
Slice disk.volume was temporarily disconnected from volume.
INFO: disk.volume: enabled slice
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Explanation
The slice disk.volume can now be accessed independently of the volume. Use the special file displayed.
INFO: disk.volume: disabled slice
Explanation
Slice disk.volume cannot be accessed any more.
INFO: disk.volume: reattached slice to volume volume
Explanation
Slice disk.volume is attached to volume again.
INFO: disk: device: ready for swapping
Explanation
The disk disk is now exchangeable.
For a file unit device supporting hot swap, you may demount the physical disk device at this point for swapping disks.
If active swap is not supported, shut down the system and turn off the power before removing the physical disk.
INFO: disk: device: ready for swapping on node node
Explanation
On the node node, the physical disk device of the disk disk is now exchangeable.
If the disk unit supports hot swap, you may simply demount device connected to node and swap disks.
If it does not support hot swap, shot down node and turn off the power, then demount device and swap disks.
INFO: disk: restored disk
Explanation
disk restored its original status.
INFO: class: class recovery completed successfully
Explanation
Recovery of the class class from the closed status succeeded.
INFO: volume: recovered volume with disk disk
Explanation
volume was recovered based on disk.
INFO: volume: recovered volume with lower level group lgroup
Explanation
Volume volume was recovered based on lower level group lgroup.
INFO: volume : recovered volume in group group
Explanation
Volume volume in group group has been recovered.
INFO: disk: recovered disk
Explanation
disk disk was recovered.
INFO: no unsynchronized slice in volume
Explanation
There is no slice that needs synchronization copying to be started, or resumed in volume.
INFO: volume: copying canceled
Explanation
Synchronization copying of volume has been cancelled.
INFO: no copying slice exists in volume
Explanation
There is no slice in the process of copying in volume.
INFO: volume: copying interrupted
Explanation
Synchronization copying on volume was canceled.
INFO: class: updated attribute value of class
Explanation
Attribute value of class was updated.
INFO: disk: updated attribute value of disk
Explanation
Attribute value of disk was updated.
INFO: group: updated attribute value of group
Explanation
Attribute value of group was updated.
INFO: volume: updated attribute value of volume
Explanation
Attribute value of volume was updated.
INFO: slice: updated attribute value of slice
Explanation
Attribute value of slice was updated.
INFO: updated /etc/vfstab fileExplanation
/etc/vfstab file has been updated.
INFO: updated /kernel/drv/sfdsk.conf fileExplanation
/kernel/drv/sfdsk.conf file has been updated.
INFO: updated /etc/system fileExplanation
/etc/system file has been updated.
INFO: completed definitions of system disk(s) mirroringExplanation
Definition for system disk mirroring is complete.
INFO: system must be rebooted:shutdown -y -g0 -i6
Explanation
Reboot the system by executing the following command.
shutdown -y -g0 -i6
INFO: completed definitions of system disk(s) mirroring cancellationExplanation
Canceling definition for system disk mirroring is complete.
INFO: disk.volume: started slice on node node
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Explanation
The slice disk.volume was activated on node. You may access the slice by using the displayed special file.
INFO: disk.volume: stopped slice on node node
Explanation
Slice disk.volume was stopped on node. You cannot access slice until it is activated again.
INFO: disk.volume: disabled slice on remote node node
Explanation
Slice disk.volume has become unavailable on remote node node.
INFO: disk.volume: current node node took over and started slice
/dev/sfdsk/class/rdsk/disk.volume
/dev/sfdsk/class/dsk/disk.volume
Explanation
The current node node took over the slice disk.volume and activated it. You may access the slice by using the displayed special file.
INFO: volume: copying parameter modification completed
Explanation
Modification of parameter related to the copying process of volume is complete.
INFO: configuration parameters modification completedExplanation
Modification of configuration parameter is complete.
INFO: proxy: related and joined to master master
Explanation
Proxy proxy has been related and joined to master master.
INFO: proxy: created proxy volume
Explanation
Proxy volume proxy has been created.
INFO: proxy: broken relation with master
Explanation
Relationship between master and proxy proxy has been cancelled.
INFO: proxy: forced to break relation with master
Explanation
Relationship between master and proxy proxy was forcibly cancelled.
INFO: proxy: must be recovered by sdxfix(1M) command
Explanation
In order to restore data of proxy proxy, volume must be restored with sdxfix(1M) command.
INFO: volume: started volume on node node,...
/dev/sfdsk/class/rdsk/volume
/dev/sfdsk/class/dsk/volume
Explanation
The volume volume started on the nodes node,.... It can be accessed with the special file.
INFO: proxy: parted from master
Explanation
Proxy proxy was parted from master.
INFO: proxy: parted from master instantly
Explanation
Proxy proxy was immediately parted from master.
INFO: proxy: rejoined to master master
Explanation
Proxy proxy has been rejoined to master master.
INFO: master: restored data from proxy proxy
Explanation
Copying from proxy proxy to master master started.
INFO: master: restored data from proxy proxy instantly
Explanation
Copying from proxy proxy to master master started. Even if the copying is in process, you may start master volumes and access valid data.
INFO: swapped slice components between master and proxyExplanation
Slice comprising proxy and slice comprising master have been swapped.
INFO: proxy: session canceled
Explanation
A session of the disk unit's copy function that resided between proxy proxy and the master was canceled.
INFO: proxy: related to master master
Explanation
Master master and proxy proxy were related and parted.
INFO: proxy: updated data with master master
Explanation
Data of proxy proxy was updated with data of master master.
INFO: proxy: updated data with master master instantly
Explanation
Data of proxy proxy was instantly updated with data of master master.
INFO: proxy: specified regions updated
Explanation
Data in the specified regions on the proxy proxy was updated.
INFO: master: specified regions restored from proxy proxy
Explanation
Based on the proxy proxy, data in the specified regions on the master master was restored.
INFO: volume: executing fsck(1M) command:
details
Explanation
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.
INFO: updated /etc/vfstab file on alternative root volume volume
Explanation
The /etc/vfstab file on the alternative root volume volume was updated.
INFO: volume will be used as dump device in alternative boot environment
Explanation
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.
INFO: updated /etc/system file on alternative root volume volume
Explanation
The /etc/system file on the alternative root volume volume was updated.
INFO: updated boot-device parameter:
old=old-boot-device ...
new=new-boot-device ...
Explanation
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.
INFO: completed definitions of switching boot environmentExplanation
The boot environment switching is now defined.
INFO: completed definitions of alternative boot environment:
current-boot-device=current-boot-device ...
alternative-boot-device=alternative-boot-device ...
Explanation
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.
INFO: class: configuration backup created
file
Explanation
The object configuration of class class was backed up in object table format to configuration file file.
INFO: configuration table converted successfully
file
Explanation
The configuration table was converted successfully. file indicates a configuration file to which the configuration table was output.
INFO: device: disk ID information not removed
Explanation
Physical disk device retains unremoved disk identification information.
INFO: class: waiting for restoration...
Explanation
Waiting for restoration of the object configuration of class class.
INFO: class: restored based on configuration file
file
Explanation
The class configuration was restored based on configuration file file.
INFO: class: current node node got class master privilege
Explanation
Current node node obtained master privileges of shared class class.
INFO: NVRAM configuration parameter has been updated,parameter='param'
Explanation
The parameter param value in device's NVRAM (nonvolatile memory) was updated.
INFO: no need to update NVRAM configuration parameter,parameter='param'
Explanation
The parameter param value in device's NVRAM (nonvolatile memory) was not updated.