ERROR: connection timeout
Explanation
Connection failed due to no response from sdxservd daemon.
Resolution
Confirm that sdxservd daemon process was started normally.
ERROR: not privileged
Explanation
Executed user is not a superuser.
Resolution
You need to have superuser authority for execution.
ERROR: option: illegal option
Explanation
option is illegal.
Resolution
See the Fix Messages described later, or the "Appendix D Command Reference."
ERROR: syntax error
Explanation
Executed command has a syntax error.
Resolution
See the Fix Messages described later, or the "Appendix D Command Reference."
ERROR: string: name too long
Explanation
Object name, file name or node identifier specified with string is too long.
Resolution
Specify the proper name.
ERROR: object: name contains invalid character "letter"
Explanation
Object name object contains an invalid character letter.
Resolution
You can only use alphanumeric characters, "-" (hyphen), and "_" (underscore) when specifying an object name.
ERROR: object: name starting with "_" or "-" is invalid
Explanation
Object name object starting with "-" (hyphen) or "_" (underscore) is invalid.
Resolution
Specify an object name that starts with an alphanumeric character.
ERROR: device: illegal physical disk name
Explanation
Physical disk name device is illegal.
Resolution
See "Appendix D Command Reference."
ERROR: object: object names must be unique within a class
Explanation
Object names within a class must be unique.
Resolution
Specify a unique object name.
ERROR: cannot be executed in non-global zone
Explanation
This command cannot be executed in a non-global zone.
Resolution
Execute the command in the global zone.
ERROR: module: environment error, details
Explanation
The command cannot be executed due to an error in the environment. The error causes only a failure in command execution but has no effect on the system. Volumes can be accessed continuously.
module is the name of the module on which this event was detected (usually an internal variable name).
details indicates the error in detail.
Resolution
Collect investigation material and contact field engineers.
ERROR: class is a shadow class
Explanation
The class class is a shadow class. The attempted operation is not supported for shadow classes.
Resolution
See "Appendix D Command Reference," and specify a correct command name and class name.
ERROR: attribute: invalid attribute name
Explanation
The same attribute has already been specified.
Resolution
See "Appendix D Command Reference."
ERROR: attribute: attribute name duplicated
Explanation
The same attribute attribute has already been specified.
Resolution
You can only specify an attribute once.
ERROR: attribute=value: invalid attribute value
Explanation
Attribute value value is invalid.
Resolution
See "Appendix D Command Reference."
If "pslice=off: invalid attribute value" is output, the possible cause is that the FJSVsdxl package of GDS may not be installed normally. If this is the cause, reinstall FJSVsdxl.
ERROR: node: node name duplicated
Explanation
The same node identifier has already been specified.
Resolution
You can only specify a node identifier once.
ERROR: too many nodes in scope
Explanation
There are too many nodes specified in scope.
Resolution
Up to 16 nodes can be specified in a scope.
ERROR: class: cannot operate shared objects, cluster control facility not ready
Explanation
Cannot operate shared objects since cluster control is not operating.
Resolution
If this message is output in the log information field of the GDS Management View, see the log file /var/opt/FJSVsdx/msglog/sdxservd.log to check when this message has been output.
Output when the command has been executed (including the operation from the GDS Management View)
Start the cluster control correctly, and execute the command again.
Output when the node has been started
When the following message is output without any other error messages of the class class after the message 60017 has been output, there is no problem and no action is required.
SDX:sdxservd: INFO: class: starting up classNone of the above
Collect investigation material and contact field engineers.
ERROR: node: remote node cannot be specified for local class
Explanation
A remote node was specified for a local class.
Resolution
Specify the node identifier of the current node for a local class.
ERROR: node: remote node cannot be specified for root class
Explanation
A remote node was specified for a root class.
Resolution
Specify the node identifier of the current node for a local class.
ERROR: current node must be specified as scope
Explanation
Current node is not specified for shared class scope.
Resolution
Always specify a node set which includes current node as scope.
ERROR: multi-nodes must be specified for shared class
Explanation
Only one node is specified for shared class scope.
Resolution
Multiple node identifiers must be specified in a scope.
ERROR: node: unknown node
Explanation
Node node does not exist.
Resolution
First check the cluster system environment. Then, try again after changing the node identifier.
ERROR: class: not shared by the current node
Explanation
Scope of class does not include the current node.
In the cluster system, class created in another node is specified.
Resolution
Execute command on a node sharing class. Or, change the specified class name.
ERROR: node: current node not active in class
Explanation
Current node node is a standby node in shared class class.
Resolution
Execute the command from another active node.
ERROR: too many disks in class
Explanation
There are too many disks registered with class.
Resolution
Create a new class.
ERROR: device: not connected to node
Explanation
The physical disk device has not been connected to the node node, or device has not been registered with the cluster resource database.
Resolution
Check the system configuration and the resource configuration.
If device has not been connected to node, specify a correct physical device name and re-execute the command.
If device has not been registered with the resource database, perform automatic resource registration to register device with the resource database, and re-execute the command.
ERROR: device: not a shared device
Explanation
Physical disk device is not a shared disk unit, or cluster shared disk definition may not be correct.
Resolution
Check the system configuration and execute the command.
ERROR: device: already exists in class
Explanation
Physical disk device is already registered with class.
Resolution
Same physical disk cannot be registered with more than one class. Specify a correct physical disk.
ERROR: device: already exists in another class
Explanation
Physical disk device is already registered with another class. This class is not shared by current node.
Resolution
Same physical disk cannot be registered with more than one class. Specify a correct physical disk.
ERROR: object: physical disk device not found
Explanation
The physical disk device that composes the object object was not found.
Resolution
The physical disk device may be connected incorrectly or a disk failure may have occurred.
Fix device connection or recover from disk failure. Alternatively, specify an object other than object.
ERROR: physical disk device not found
Explanation
The physical disk device was not found.
Resolution
The physical disk device may be connected incorrectly or a disk failure may have occurred.
Fix device connection or recover from disk failure.
ERROR: device: no such device
Explanation
There is no physical disk device.
Resolution
Specify a correct physical disk name.
ERROR: device: cannot open, errno=errno
Explanation
Cannot open physical disk device.
Resolution
Confirm that physical disk device is operating normally.
ERROR: device: not a hard disk
Explanation
Physical disk device is not a hard disk.
Resolution
GDS cannot manage devices other than hard disks.
ERROR: device: disk driver driver not supported
Explanation
Physical disk unit with the driver name driver is not supported.
Resolution
There is no resolution.
ERROR: device: illegal format
Explanation
Physical disk device format is illegal.
Resolution
Check the format status.
ERROR: object: device busy
Explanation
Object object is in use.
Resolution
Change to unused status and execute the command again.
ERROR: object: linked to a cluster service
Explanation
Object object is used in a cluster application.
Resolution
Check the cluster environment settings.
ERROR: device: configuration information exists in private slice
Explanation
Configuration information exists in the private slice of physical disk device, and registering device failed.
The following events a) to d) are the possible causes.
a) device is already registered with another class.
b) device is registered with a class in another domain.
c) The entire SDX disk was copied or is being copied to device with the disk unit's copy function.
d) After registering device with the class, it was not removed normally, and the private slice and configuration information remain existent in device illegally.
Resolution
Check the system configuration and so on, and identify the cause among a) to d). If the cause is a) or b), specify a physical disk not registered with a class. If it is c) or d), use the format(1M) command to remove the private slice from a physical disk device as needed.
For a root class, the slice whose tag is 33 is the private slice. The value of the slice tag can be checked with the prtvtoc(1M) command. For local and shared classes, slice 0 is the private slice.
ERROR: device: type cannot be specified except undef
Explanation
The class scope includes a node to which physical disk device is unconnected and the type can only be set to "undef" for registering device to the class.
Resolution
See "Appendix D Command Reference."
ERROR: class: device: type cannot be specified except undef
Explanation
Class class includes a switch group and the type can only be set to "undef" for registering physical disk device to class.
Resolution
See "Appendix D Command Reference."
ERROR: device: write error, errno=errno
Explanation
A write error occurred in physical disk device.
Resolution
A disk failure may have occurred. Identify the cause by referring to disk driver log messages and so on, and recover the disk.
If device is a write-locked disk that is connected to a switch group, register writable disks first.
ERROR: device: disk ID information differs from all disks in specified class
Explanation
The specified class includes no disk with the same disk ID information (class name and disk name) as that stored in the private slice of physical disk device. For this reason, device cannot be registered with the specified class.
Resolution
Check the system configuration and so on, and specify a physical disk and class name properly.
ERROR: object: name already assigned to another object
Explanation
Object name object already exists within class. You cannot create multiple objects with the same name.
Resolution
Specify another name and execute the command again.
ERROR: cannot connect to sdxcld
Explanation
Connecting to sdxcld, a GDS cluster linked daemon was unsuccessful.
Resolution
When unable to identify the cause, collect investigation material and contact field engineers.
ERROR: physical device driver returned an error, errno=errno
Explanation
Physical disk driver returned an error.
Resolution
Identify the cause by referring to error number and message log.
ERROR: special file operation failed, errno=errno
Explanation
Operating special file was unsuccessful.
Resolution
Identify the cause by referring to error number and GDS log message.
ERROR: sfdsk driver returned an error, errno=errno
Explanation
GDS driver returned an error.
Resolution
Identify the cause by referring to error number, GDS log message, and syslog message.
ERROR: sfdsk driver returned a temporary error, try again for a whileExplanation
GDS driver returned a temporary error.
Resolution
Execute the command again after a while.
ERROR: class: class closed down
Explanation
class is closed. You cannot operate objects within a closed class.
Resolution
A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: class: class closed down on another node
Explanation
class is closed on another node. You cannot operate objects within a closed class.
Resolution
Recover closed class. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: keep disk cannot be specified for local or shared classExplanation
Keep disk cannot be registered with local or shared class.
Resolution
Register keep disk with root class.
ERROR: too many keep disks specifiedExplanation
The number of specified keep disks exceeds that of undefined disks.
Resolution
When registering multiple keep disks, specify the same number or more as undefined disks at the same time.
ERROR: class: already root class exists
Explanation
You tried to create a new class when there is already a root class. You can only create one root class within a node.
Resolution
Specify the existing root class or a local class.
ERROR: pslice is not backup slice, correct slice tag and size by format(1M) command
Explanation
Physical slice pslice is not a backup slice.
Resolution
Change the tag of physical slice pslice to "backup" with the format(1M) command and change its size to that of total disk cylinders available in the entire disk.
ERROR: device contains overlapping slices
Explanation
Physical disk device contains a physical slice with overlapping cylinder.
Resolution
Use the format (1M) command and correct the physical slice configuration.
ERROR: device: one or more free slices are required, change a slice size to 0 by format(1M) command
Explanation
The number of slices created on the physical disk device has reached the upper limit (seven). The slice numbers are all in use and device cannot be registered as a keep disk.
Resolution
Use the format(1M) command to remove one or more slices from device.
ERROR: pslice: invalid partition tag, tag=tag_num
Explanation
Partition tag value tag_num for physical slice pslice is invalid.
Resolution
Change the tag of pslice to "unassigned" or the size of pslice to 0 (zero) with the format(1M) command.
ERROR: device: no enough unassigned disk space, reserve enough space by format(1M) command
Explanation
Physical disk device does not have sufficient free disk space.
Resolution
Use the format (1M) command and create sufficient free disk space or swap area.
For the size see "A.2.7 Disk Size."
ERROR: device: no unassigned disk space nor swap space, reserve enough space by format(1M) command
Explanation
Physical disk device does not have free disk space or swap area.
Resolution
Use the format (1M) command and create sufficient free disk space or swap area.
For the size see "A.2.7 Disk Size."
ERROR: device: no enough unassigned disk space nor swap space, reserve enough space by format(1M) command
Explanation
Physical disk device does not have sufficient free disk space or swap area.
Resolution
Use the format (1M) command and create sufficient free disk space or swap area.
For the size see "A.2.7 Disk Size."
ERROR: pslice: too large swap device
Explanation
The size of the swap device pslice is too large. In 32-bit Solaris, a disk with the swap device of which size is equal to or larger than 2 GB cannot be registered with the root class as the keep disk.
Resolution
Reduce the swap disk size to a size smaller than 2 GB. Alternatively, change the system to 64-bit Solaris.
ERROR: device: invalid physical device, managed by driver
Explanation
Specified physical disk is managed by driver, and is therefore invalid.
Resolution
Confirm the I/O and cluster system configuration, and specify a correct physical disk name.
ERROR: device: disk driver driver not supported for root class
Explanation
Physical disk device with driver name driver cannot be registered with root class.
Resolution
Register the disk with local class or shared class as needed.
ERROR: device: IDE disk cannot be specified as spare disk
Explanation
The device is an IDE disk. It cannot be used as a spare disk.
Resolution
For spare disks, use disks other than IDE disks.
ERROR: class: no such class
Explanation
Cannot find class.
Resolution
Check GDS configuration.
ERROR: group: not a group
Explanation
group is not a group name.
Resolution
There is another object with the name group within class. Check configuration.
ERROR: group is a lower level stripe group
Explanation
Group group is a stripe group connected to another group. Disks and groups cannot be connected to or disconnected from group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: group: connected to a lower level stripe group
Explanation
Group group is connected to a lower level stripe group. Disks and groups cannot be connected to or disconnected from group.
Resolution
Disconnect the higher level stripe group of group from its higher level group as necessary.
ERROR: too many groups in class
Explanation
Class class already has the maximum number of groups possible. A maximum of 100 groups can be created within, and a maximum of 1024 groups can be created within a local class or a shared class.
Resolution
Create a new class.
ERROR: too many disks and/or groups are connected to group
Explanation
The maximum number of disks or lower level groups are already connected to group group.
Resolution
There is no resolution.
ERROR: object: smaller than stripe width of group group
Explanation
Since the available size of disk or lower level group indicated by object is smaller than the stripe width of group group, object cannot be connected to group.
Resolution
Execute the command after indicating a disk or lower level group with sufficient size, or remove group group and adjust the stripe width to a smaller size.
ERROR: class: three or more nodes exist in class scope
Explanation
The scope of class class includes 3 or more nodes. Classes whose scope includes 3 or more nodes cannot include switch groups.
Resolution
Specify a shared class of which scope is 2 nodes.
ERROR: disk: type disk exists in class
Explanation
Class class includes disk disk of the type type. The attempted operation is not supported for classes that include type type disks.
Resolution
Delete disk from class as needed and re-execute the command.
ERROR: class includes a group that cannot exist together with a switch group
Explanation
The class class includes one of the following groups and a switch group cannot be created.
Mirror group
Stripe group
Concatenation group to which any lower level switch group is not connected
Resolution
Specify a correct class name.
ERROR: active disk must be specified
Explanation
When creating a switch group, specify the active disk in the -a actdisk=disk option.
Resolution
Specify the option properly, referring to "Appendix D Command Reference."
ERROR: disk: active disk not specified by -d option
Explanation
Active disk disk was not specified in the -d option.
Resolution
When creating a switch group, specify one of the disks specified in the -d option of the sdxdisk -C command as the active disk.
ERROR: too many disks specified
Explanation
Too many disks specified.
Resolution
Specify a proper number of disks.
For the number of disks that can be connected to a group, see " A.1.3 Number of Disks."
ERROR: disk: physical scope is not included in class scope
Explanation
The physical scope of disk disk is not included in the class scope and disk cannot be connected to a switch group.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: physical scope must be same as class scope
Explanation
The physical scope of the active disk matches the class scope and therefore the physical scope of an inactive disk must match the class scope. The physical scope of disk disk does not match the class scope and disk cannot be connected to the switch group as the inactive disk.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: physical scope must include only node
Explanation
The physical scope of inactive disk disk can include only node node.
Resolution
Specify a correct disk name, referring to "Appendix D Command Reference."
ERROR: disk: class scope is not included in physical scope
Explanation
The class scope is not included in the physical scope of disk disk and disk cannot be connected to a group other than a switch group.
Resolution
Specify a correct disk name. For the physical scope of a disk, use the sdxinfo -D command and check the displayed DEVCONNECT field. For the class scope, use the sdxinfo -C command and check the displayed SCOPE field.
ERROR: disk: no such disk
Explanation
There is no disk.
Resolution
Check GDS configuration.
ERROR: object: already connected to group
Explanation
Disk or group indicated by object, is already connected to group group.
Resolution
Specify a correct disk name or group name.
ERROR: disk is a spare disk
Explanation
disk is a spare disk. You cannot connect a spare disk to a group.
Resolution
Change the disk attributes to undefined, and execute the command again.
ERROR: object not in status status
Explanation
Object status is not status status.
Resolution
Confirm that object status is status, and execute the command again.
ERROR: object too small
Explanation
The size of object is too small.
Resolution
Check the necessary object size and specify a larger object.
ERROR: another disk must be connected to group
Explanation
You must connect another disk to group.
Resolution
Connect another disk and execute the command again.
ERROR: invalid physical slice number, pslice_num
Explanation
Invalid physical slice number pslice_num is specified.
Resolution
For physical slice number pslice_num, specify an integer from 0 to 7, excluding 2.
ERROR: pslice is backup slice
Explanation
Physical slice pslice is a backup slice.
Resolution
For physical slice number, specify an integer from 0 to 7, excluding 2.
ERROR: pslice is private slice
Explanation
Physical slice pslice is a private slice.
Resolution
Do not specify a private slice for physical slice number.
ERROR: pslice: corresponding volume attributes must be specified
Explanation
Volume attributes corresponding to physical slice pslice is not specified.
Resolution
See "Appendix D Command Reference."
ERROR: object: invalid size
Explanation
Object size of object is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: two or more keep disks cannot be connected to a groupExplanation
More than one keep disk cannot be connected to group.
Resolution
See "Appendix D Command Reference."
ERROR: two or more single disks cannot be connected to a groupExplanation
More than one single disk cannot be connected to a group.
Resolution
See "Appendix D Command Reference."
ERROR: both keep and single disks cannot be connected to a groupExplanation
Both keep and single disks cannot be connected to a group at the same time.
Resolution
See "Appendix D Command Reference."
ERROR: disk: keep disk cannot be connected to existing group
Explanation
Keep disk disk cannot be connected to an existing group.
Resolution
See "Appendix D Command Reference."
ERROR: disk: single disk cannot be connected to existing group
Explanation
Single disk disk cannot be connected to the existing group.
Resolution
See "Appendix D Command Reference."
ERROR: two or more IDE disks cannot be connected to a groupExplanation
More than one IDE disk cannot be connected to a group.
Resolution
When mirroring an IDE disk, use it with disks other than IDE disks.
ERROR: two or more disks cannot be connected to a groupExplanation
If the FJSVsdxl package of GDS is not installed, multiple disks cannot be connected to a group.
Resolution
If FJSVsdxl has not been installed normally, reinstall it.
ERROR: group: a lower level switch group is connected
Explanation
A switch group has been connected to the group group and it is impossible to connect a disk to group or group to another group.
Resolution
Specify a correct higher level group name.
ERROR: disk: not a bootable device
Explanation
Disk disk cannot be booted.
Resolution
Confirm the disk configuration. When you cannot specify the cause, collect investigation material and contact field engineers.
ERROR: too few valid configuration database replicasExplanation
There is not sufficient valid configuration database for class. This message is displayed when the majority of disks registered with class are unavailable.
Leaving it as is may cause serious problems.
Resolution
For details, see "F.1.4 Class Status Abnormality."
ERROR: group: no ENABLE disk in group
Explanation
Group group does not have a disk in ENABLE status connected.
Resolution
See "F.1.2 Disk Status Abnormality" and recover disks connected to the group.
ERROR: msec: invalid delay value
Explanation
Delay time msec is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: lgroup: mirror group cannot be connected to another group
Explanation
Since group lgroup is a mirror group, it cannot be connected to another group.
Resolution
Specify a correct lower level group name.
ERROR: lgroup: same type as higher level group hgroup
Explanation
Since the type attributes for group lgroup and higher level group hgroup are the same, lgroup cannot be connected to hgroup.
Resolution
Specify a correct group name.
ERROR: hgroup: same name as a lower level group
Explanation
For the higher level group name, name hgoup, which is the same as the lower level group was indicated.
Resolution
Different names must be indicated for higher level group and lower level group.
ERROR: hgroup: any group cannot be connected to a switch group
Explanation
Group hgroup is a switch group and any group cannot be connected to.
Resolution
Specify a correct group name.
ERROR: group: is a lower level concatenation group
Explanation
The group group is a concatenation group connected to another group. Any group cannot be connected to group.
Resolution
Disconnect group from the higher level group as needed and re-execute the command.
ERROR: lgroup: stripe group cannot be connected to concatenation group
Explanation
The group lgroup is a stripe group and cannot be connected to a concatenation group.
Resolution
Specify a correct group name.
ERROR: lgroup: switch group cannot be connected to mirror group
Explanation
The group lgroup is a switch group and cannot be connected to a mirror group.
Resolution
Specify a correct group name.
ERROR: lgroup: switch group cannot be connected to stripe group
Explanation
The group lgroup is a switch group and cannot be connected to a stripe group.
Resolution
Specify a correct group name.
ERROR: hgroup: disk is connected
Explanation
A disk is already connected to concatenation group hgroup, and a switch group cannot be connected.
Resolution
Specify a correct group name.
ERROR: size: must be more than zero
Explanation
size must be a positive integer.
Resolution
Specify the correct size.
ERROR: size: invalid size
Explanation
The indicated size size is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: group: no such group
Explanation
There is no group.
Resolution
Specify a correct group name.
ERROR: group: not the highest level group
Explanation
Group group is not the highest level group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: too many volumes exist in object
Explanation
The maximum number of volumes, already exists in the object, that is a class, a group, or a single disk.
Resolution
Create volumes in another group or on a single disk as needed.
ERROR: too many volumes with physical slices in object
Explanation
In the object, the number of volumes which consist of physical slices has reached the maximum. object is a name of group or single disk.
Resolution
Change the physical slice attributes for volumes in object from on to off using the sdxattr -V command as needed, and execute the command again.
ERROR: group: volume with physical slice(s) cannot be created
Explanation
Although a physical slice cannot be created in group group, an attempt was made to create a volume with one or more physical slices.
Resolution
Create a volume without any physical slice for group either by:
Turning "off" the [Physical Slice] option in the Volume Configuration dialog box when creating the volume for group in GDS Management View
Using the -a pslice=off option when creating the volume for group with the sdxvolume -M command
If group is a mirror group, connect one or more disks to the group in order to create a volume with a physical slice.
ERROR: object: no enough space
Explanation
There is not enough space in the group or single disk indicated by object.
Resolution
Change the size you specify as needed.
After expanding the physical disk size of the group or single disk specified by object, if the volume size in the group or single disk is expanded by the sdxvolume -S command, this message is output. In this case, take one of the following actions.
Perform the following operations for the physical disk of which the size was expanded.
a1) Make the physical disk exchangeable with the sdxswap -O command or [Swap Physical Disk].
a2) Restore the status with the sdxswap -I command or [Restore Physical Disk].
b1) Perform the following operations for the group or single disk specified by object.
b1-1) Back up the data of all of the volumes in object.
b1-2) Delete all of the volumes from object.
b2) Perform the following operations for the disk of which the size was expanded.
b2-1) When the disk is connected to the group, disconnect the disk from the group.
b2-2) Make the physical disk exchangeable with the sdxswap -O command or [Swap Physical Disk].
b2-3) Restore the status with the sdxswap -I command or [Restore Physical Disk].
b2-4) If the disk is disconnected from the group in step b2-1), connect the disk to the group again.
b3) Perform the following operations for the group or single disk specified by object.
b3-1) Recreate the volume deleted in step b1-2).
b3-2) Restore the data of volume backed up in step b1-1).
c1) Perform the following operations for the group or single disk specified by object.
c1-1) Back up the data of all of the volumes in object.
c1-2) Delete all of the volumes from object.
c2) Perform the following operations for the disk of which the size was expanded.
c2-1) When the disk is connected to the group, disconnect the disk from the group.
c2-2) Delete the disk from the class.
c2-3) Register the disk to the class again.
c2-4) If the disk is disconnected from the group in step c2-1), connect the disk to the group again.
c3) Perform the following operations for the group or single disk specified by object.
c3-1) Recreate the volume deleted in step c1-2).
c3-2) Restore the data of volume backed up in step c1-1).
ERROR: disk: not a single disk
Explanation
The disk disk is not a single disk.
Resolution
Specify a correct disk name.
ERROR: disk: status disk connected to group
Explanation
disk in status status is connected to group.
Resolution
Restore the status of disk and execute the command again.
ERROR: status disk exists in group
Explanation
The disk in status status is connected to group, or it connected to the lower level group of group.
Resolution
Confirm the disk status, and please execute a command again after canceling the status status if necessary.
ERROR: disk: no such disk in group
Explanation
disk is not connected to group.
Resolution
Specify a correct disk name and group name.
ERROR: disk: device: device busy
Explanation
Disk disk (physical disk name is device ) is in use.
Resolution
Change to unused status, and execute the command again.
ERROR: too many nodes specifiedExplanation
Too many nodes were specified.
Resolution
Specify the nodes included in the scope of the class.
ERROR: option: cannot be specified for root nor local class
Explanation
Command option option cannot be specified for a root nor local class.
Resolution
See "Appendix D Command Reference."
ERROR: node: not in scope, class=class
Explanation
Node node is not included in the scope of the class class.
Resolution
Confirm your GDS configuration, specify a node included in the scope of the class, and try the command again.
ERROR: volume: cannot start, class closed down, node=node
Explanation
Starting volume volume was unsuccessful due to the class to which volume volume belongs was blockading it on node node.
Resolution
Recover the blockage of the class to which volume volume belongs. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: volume: no such volume
Explanation
There is no volume.
Resolution
Specify a correct volume name.
ERROR: object in status status
Explanation
object is in status status.
Resolution
Confirm the object status, and cancel the status status if necessary.
ERROR: some ACTIVE volumes exist in class, node=node
Explanation
Volumes of class class are already active on node node, and volumes of class cannot be started or created on this node.
Resolution
Create volumes of class class on node node. Alternatively, as needed, stop all the volumes within class on node and then start or create volumes on this node.
If a cluster application to which class resources are registered is operating or is standby on node, before stopping volumes on node, stop the cluster application.
ERROR: volume: some ACTIVE volumes exist in class, node=node
Explanation
Volumes of class class are already active on node node, and volume volume cannot be started on this node.
Resolution
Stop all the volumes within class class on node node as needed, start volume volume on this node.
If a cluster application to which class resources are registered is operating or is standby on node, before stopping volumes on node, stop the cluster application.
ERROR: volume: active disk not connected to node
Explanation
The active disk of a switch group including switch volume volume is not connected to node node and the volume cannot be started on the node.
Resolution
If an inactive disk is connected to a switch group including volume, use the sdxattr -G command and switch the inactive disk to the active disk in order to start volume on node.
ERROR: volume: active disk of lower level group group is not connected to node
Explanation
The active disk of lower level switch group group is not connected to node node, and volume volume cannot be started on node. group is a lower level switch group that is connected to the highest level group to which volume belongs.
Resolution
If an inactive disk is connected to group, switch the active disk to the inactive disk with the sdxattr -G command in order to enable volume startup on node.
ERROR: lock is set on volume volume, node=node
Explanation
The "Lock volume" mode for volume volume on node node is turned on.
Resolution
Turn off the "Lock volume" mode, or use the -e unlock option as necessary.
ERROR: volume: cannot stop, class closed down, node=node
Explanation
Stopping volume volume was unsuccessful due to the class to which volume volume belongs was blockading it on node node.
Resolution
Recover the blockage of the class to which volume volume belongs. A number of disk failures may have occurred. Identify the cause by referring to object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: object.volume: status slice exists in object
Explanation
Slice object.volume in status status exists in object.
Resolution
Confirm the object status, and cancel the status status if necessary.
ERROR: object in status status, node=node
Explanation
object on node is in status status.
Resolution
Confirm the object status, and cancel the status status if necessary.
ERROR: volume: stripe type volume cannot be resized
Explanation
The volume volume cannot be resized since it is a volume created in a stripe group.
Resolution
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "A.2.30 Online Volume Expansion."
ERROR: volume: concat type volume cannot be resized
Explanation
The volume volume cannot be resized since it is a volume created in a concatenation group.
Resolution
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "A.2.30 Online Volume Expansion."
ERROR: volume: consists of multiple mirror slices
Explanation
The volume volume cannot be resized since it is a mirror volume that consists of multiple mirror slices.
Resolution
Disconnect disks and lower level groups from the mirror group so that volume is composed of only one mirror slice, and try this command again.
ERROR: spare disk connected for disk
Explanation
Spare disk is connected instead of disk.
Resolution
First recover the disk status.
ERROR: object.volume is only valid slice
Explanation
object.volume is the only valid slice within volume volume. You cannot continue your operation because data within volume may be lost if you continue your operation.
Resolution
If volume is a mirror volume, you will be able to continue your operation by recovering the mirroring (for example, by connecting a new disk to group).
If volume is not a mirror volume, remove volume as necessary.
ERROR: object: the last disk or group in lower level group group
Explanation
Object object is the only disk or group connected to the lower level group group. You cannot disconnect object from group.
Resolution
Disconnect group from the higher level group as necessary.
ERROR: object: not connected to the end of concatenation group group
Explanation
The object object is not the disk or switch group that was last connected to the concatenation group group. It is impossible to disconnect object from group.
Resolution
To disconnect disks and groups from group, perform disconnection in inverse order of connection. For the order of connecting disks and groups to group, use the dxinfo -G command and check the displayed DISKS field.
ERROR: object: disk space is assigned to volume volume
Explanation
Disk space of disk or lower switch group object is assigned to volume volume, and object cannot be disconnected from the concatenation group.
Resolution
If needed, remove volume first.
ERROR: group: inactive disk is connected
Explanation
The group group has a connected inactive disk and physical disk swap or disconnection cannot be performed for the active disk of the group.
Resolution
As needed, switch the active disk with the sdxattr -G command and perform physical disk swap or disconnection for the previous active disk.
ERROR: disk: not inactive disk
Explanation
The disk disk is the active disk of a lower level switch group, and physical disk swap cannot be performed.
Resolution
As needed, switch the active disk with the sdxattr -G command, and perform physical disk swap on the previous active disk.
ERROR: lgroup: no such group in hgroup
Explanation
Group lgroup is not connected to group hgroup.
Resolution
Specify a correct group name.
ERROR: one or more volumes exist in group
Explanation
One or more volumes exist in group group.
Resolution
First, remove the volume if necessary.
ERROR: disk connected to group
Explanation
disk is connected to group.
Resolution
First, disconnect the disk from group if necessary.
ERROR: disk: The last ENABLE disk in class cannot be removed
Explanation
When there is a disk in SWAP or DISABLE status in class, you cannot remove the last disk in ENABLE status.
Resolution
First recover the disk in SWAP or DISABLE status. Or, you can register a new disk with class.
ERROR: disk: cannot be removed to avoid class closing down
Explanation
Disk disk stores the configuration database and removal of disk will result in class closure. For this reason, the disk cannot be removed.
Resolution
Recover or remove a failed disk in the class that includes disk and then remove disk.
ERROR: one or more volumes exist in disk
Explanation
Volume exists in disk.
Resolution
First, remove the volume as needed.
ERROR: one or more groups exist in class
Explanation
Group exists in class.
Resolution
First, remove the group as needed.
ERROR: disk: status disk exists in class
Explanation
disk in status status exists in class.
Resolution
First, restore the disk in status status.
ERROR: volume: status volume exists in class, node=node
Explanation
volume in status status on node exists in class.
Resolution
First, change the volume status as needed.
ERROR: disk: no such disk
Explanation
There is no disk disk.
Resolution
Specify a correct disk name.
ERROR: volume: not associated with object
Explanation
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
Resolution
See "Appendix D Command Reference" and specify a correct disk or group name and volume name.
ERROR: volume is single volume
Explanation
Volume is a single volume. Slices of single volumes cannot be detached.
Resolution
Specify a correct volume name.
ERROR: volume: not a mirror volume
Explanation
Volume volume is not a mirror volume.
Resolution
Specify a correct volume name.
ERROR: object: not connected to the highest level group
Explanation
Disk or group indicated by object is not connected to the highest-level group.
Resolution
See "Appendix D Command Reference" and specify a correct disk name or group name.
ERROR: disk: The last ENABLE disk in class cannot be swapped
Explanation
You cannot swap the last ENABLE status disk in class.
Resolution
Depending on the configuration, use a different method to avoid such situations. For example, you can register a new disk with class.
ERROR: disk: keep disk cannot be swapped out
Explanation
Keep disk disk cannot be swapped.
Resolution
Change the type attribute of disk, and execute the command again.
ERROR: disk: volume in status status
Explanation
There is a volume related to disk in status status.
Resolution
First, recover the volume in status status.
ERROR: disk: the highest level group is not a mirror group
Explanation
The highest level group of disk disk is not a mirror group.
You cannot swap disk.
Resolution
Disconnect disk from the group, and execute the command in a situation where it is not connected to any group.
ERROR: disk: cannot be swapped to avoid class closing down
Explanation
The disk disk stores the configuration database and swapping disk will close down the class. Therefore, swapping the disk is prevented.
Resolution
Replace a failed disk included in the class to which disk is registered and swap disk.
ERROR: disk: device: device busy on node node
Explanation
Disk disk (the physical disk name is device) is in use on node.
Resolution
Change the status to unused and execute the command again.
ERROR: disk: device: cannot open, errno=errno
Explanation
Cannot open physical disk device.
Resolution
Confirm that physical disk device is operating normally.
ERROR: disk: device: not a hard disk
Explanation
Physical disk device is not a hard disk.
Resolution
Specify a hard disk.
ERROR: disk: device: illegal format
Explanation
Physical disk device format is illegal.
Resolution
Check the format of the physical disk.
ERROR: disk busy - /dev/rdsk/pslice
Explanation
Physical disk pslice is in use.
Resolution
Change to unused status and execute the command again.
ERROR: disk: device: linked to a cluster service
Explanation
Physical disk device is used in a cluster application.
Resolution
Check the settings for cluster environment.
ERROR: disk: device: not enough size
Explanation
Physical disk size is too small.
Resolution
Specify a physical disk with sufficient size.
ERROR: disk: device: not connected to node
Explanation
Physical disk device is not connected to node. Or, cluster shared disk definition may not be correct.
Resolution
Check the system configuration and execute the command.
ERROR: disk: device: invalid disk, managed by driver
Explanation
Specified disk (corresponding physical disk name is device) is managed by driver, and is therefore invalid.
Resolution
Confirm the I/O and cluster system configuration, and specify a correct physical disk name.
ERROR: object.volume: status slice exists in group
Explanation
Slice object.volume in status status already exists in group group.
Resolution
Check the object status and cancel status status if necessary.
ERROR: disk : device : invalid disk on node node, managed by driver
Explanation
On node node, physical disk device of disk disk has been managed by driver driver and cannot be handled.
Resolution
Check I/O configurations and cluster system configurations, and specify a correct physical disk name.
ERROR: disk : device : cannot open on node node, errno=errno
Explanation
Physical disk device cannot be opened on node node.
Resolution
Check whether or not the physical disk device is operating normally.
ERROR: disk : device : node : not a hard disk
Explanation
Physical disk device on node node is not a hard disk.
Resolution
Specify a hard disk.
ERROR: disk : device : node : illegal format
Explanation
The format of physical disk device on node node is incorrect.
Resolution
Check the format.
ERROR: disk busy on node node - /dev/rdsk/pslice
Explanation
Physical disk pslice on node node is in use.
Resolution
Change the status to unused and retry the command.
ERROR: disk : device : node : linked to a cluster service
Explanation
Physical disk device on node node is being used by cluster applications.
Resolution
Check the cluster environment configurations.
ERROR: disk : device : node: not enough size
Explanation
The size of physical disk device on node node is too small.
Resolution
Replace it with a physical disk of sufficient size.
ERROR: disk : device : read error, errno=errno
Explanation
A read error occurred on physical disk device.
Resolution
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
ERROR: disk : device : node: read error, errno=errno
Explanation
A read error occurred on physical disk device on node node.
Resolution
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
ERROR: object: read error, errno=errno
Explanation
Read error occurred on the disk indicated by object, or on a disk connected to group indicated by object, or on a disk connected to a lower level of the group indicated by object.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk. Otherwise, indicate another disk or group that is normal.
ERROR: object.volume : no such slice
Explanation
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
Resolution
See "Appendix D Command Reference" and specify a correct disk or group name and volume name.
ERROR: disk: not active disk
Explanation
Disk disk is not the active disk.
Resolution
Specify the active disk.
ERROR: disk: I/O error not occur
Explanation
An I/O error has not been occurred on the disk disk. There is no need to restore disk using the sdxfix -D command.
Resolution
There is no resolution.
ERROR: class: not close down
Explanation
Class class is not closed. Recovery class with the sdxfix -C command is not required.
Resolution
There is no resolution.
ERROR: no valid configuration databaseExplanation
No valid configuration database of the class is found. If all (or most of) the disks that are registered with the class are unavailable, this message is output.
Resolution
ERROR: class: closed down on all nodes in class scope
Explanation
During recovery of class class from the closed status, class was closed on all the nodes within the class scope.
Resolution
Re-execute the sdxfix -C command.
ERROR: disk: connected to switch group
Explanation
Disk disk is connected to a switch group and an I/O error status of the disk cannot be removed.
Resolution
Make disk exchangeable with the sdxswap -O command or [Operation]:[Swap Physical Disk] in GDS Management View to remove an I/O error status of disk. After this procedure, swap the physical disks of disk according to need and then make the disk usable again with the sdxswap -I command or [Operation]:[Restore Physical Disk] in GDS Management View.
ERROR: volume: cannot restart to copy, cancel current interrupted copy operation by sdxcopy command with -C option
Explanation
Copying process within volume could not be resumed.
Resolution
Cancel the interrupted copying process according to need and resume copying.
ERROR: attribute=value: cannot modify type attribute of root class
Explanation
The root class type attribute cannot be changed.
Resolution
Specify a correct class name.
ERROR: class: class names must be unique within a domain
Explanation
Class class with the same name as class already exists within the cluster domain.
Resolution
When renaming a class resulted in this message, specify another class name.
When expanding the class scope resulted in this message, see "Important Point 2" in "A.2.34 Changing Over from Single Nodes to a Cluster System."
ERROR: class: volume minor numbers must be unique within a domain
Explanation
A volume with the same minor number as that of a volume in the class class was found within the cluster domain.
Resolution
ERROR: one or more disks not connected to node
Explanation
Disks that are not connected to node node or for which disk resources are not created yet exist in the class.
Resolution
Check the hardware configuration and the disk configuration within the class. If disk resources are not created yet, create those through the automatic resource registration.
For the automatic resource registration, see "PRIMECLUSTER Installation and Administration Guide."
ERROR: disk: IDE disk cannot be specified as spare disk
Explanation
The disk is an IDE disk. It cannot be used as a spare disk.
Resolution
For spare disks, use disks other than IDE disks.
ERROR: object: no such object
Explanation
There is no object.
Resolution
Specify a correct object name.
ERROR: class: shared objects information not yet available, try again for a while
Explanation
Share object information is not available yet.
Resolution
Wait until cluster control is activated, and execute the command again.
ERROR: node: node in stopped status
Explanation
You cannot proceed with operation since node is in stopped status.
Resolution
Start the node and try again.
ERROR: node: node in abnormal status
Explanation
node is in an abnormal status and cannot proceed with operation.
Resolution
Confirm the normal startup of node and try again.
ERROR: cluster communication failureExplanation
Cannot proceed with operation since communication failed with cluster.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: cluster communication failure, sdxerrno=sdxerrno
Explanation
Cannot proceed with operation since communication failed with cluster.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: cluster communication failure, remote-node=node, sdxerrno=sdxerrno
Explanation
Cluster communication with remote node node failed. Operation cannot be performed.
Resolution
Check that the cluster system and GDS are operating normally.
After recovering, try again.
ERROR: class: not a root class
Explanation
Class class is not a root class. The possible causes are as follows.
a) The specified class name is wrong.
b) An attempt to use a function that is only for a root class was made for a local class or a shared class.
c) In a system where the FJSVsdxl package of GDS is not installed normally, an attempt to create a local class group or a shared class group was made.
d) In a system where the FJSVsdxsl package of GDS Snapshot is not installed normally, an attempt to perform proxy operation was made for a local class or a shared class.
Resolution
If the cause is a) or b), see "Appendix D Command Reference" and specify a correct class name. If it is c) or d), install FJSVsdxl or FJSVsdxsl normally.
ERROR: disk: not a keep disk
Explanation
Disk disk is not a keep disk.
Resolution
See "Appendix D Command Reference" and specify a correct disk name.
ERROR: disk: not connected to any group
Explanation
Disk disk is not connected to a group.
Resolution
See "Appendix D Command Reference" and specify a correct disk name.
ERROR: volume: status volume exists in group
Explanation
There is volume in status status in group.
Resolution
Recover volume status, and execute the command again.
ERROR: disk: not a system disk
Explanation
Disk disk is not a system disk.
Resolution
Specify a correct disk name, and execute the command again.
ERROR: device: mandatory system disk must be registered to class
Explanation
The system disk device is not registered with the class class. device contains the slice currently operating as / (root), /usr, or /var, and to perform system disk setting, it is necessary to register device with class.
Resolution
Complete preparations properly referring to "5.2.1 System Disk Settings" or "Appendix D Command Reference" and execute the command again.
ERROR: disk: mandatory system disk must be specified
Explanation
The system disk disk was not specified. disk contains the slice currently operating as / (root), /usr, or /var, and to cancel disk mirroring, it is necessary to specify disk.
Resolution
Specify all system disks with the slices currently operating as / (root), /usr, or /var, and execute the command again.
ERROR: disk: two or more disks connected to group
Explanation
group to which disk is connected has two or more disks connected.
Resolution
See "Appendix D Command Reference" and complete preparation correctly. Then execute the command again.
ERROR: root file system not mounted on volumeExplanation
Root file system is not mounted on volume.
Resolution
Confirm the configuration, and see "Appendix D Command Reference."
ERROR: illegal slice nameExplanation
Slice name includes a "." (period).
Resolution
Specify the correct slice name.
ERROR: disk.volume cannot be operated on the current node, take over by sdxslice command with -T option
Explanation
Slice disk.volume cannot be operated on the current node.
Resolution
Take over the slice by executing sdxslice -T command.
ERROR: volume: physical slice attribute value is off
Explanation
The physical slice attribute value of volume volume is "off." A slice in a volume without physical slices cannot be detached.
Resolution
Retry the command after turning the physical slice attribute of volume to be "on" according to need.
ERROR: object: device busy on node node
Explanation
object is in use on node.
Resolution
Change to unused status and execute the command again.
ERROR: class: not a shared class
Explanation
class is not a shared class.
Resolution
Specify a shared class.
ERROR: param: invalid parameter name
Explanation
Parameter name param is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: param =val: invalid parameter value
Explanation
Parameter value val is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: param: parameter name duplicated
Explanation
The same parameter name param has already been specified.
Resolution
You can only use a parameter name once.
ERROR: copy_concurrency=val: value more than or equal to the number of actually running copy operations must be specified
Explanation
Value smaller than the number of copying currently in process has been specified for copy_concurrency parameter.
Resolution
Set a value more than or equal to the number of copying currently in process for copy_concurrency parameter.
ERROR: mode=string: access mode duplicated
Explanation
Multiple access modes have been specified.
Resolution
Specify only one access mode.
ERROR: mode=string: invalid access mode
Explanation
Access mode value string is invalid.
Resolution
See "Appendix D Command Reference."
ERROR: volume: already started with different access mode, node=node
Explanation
On the node node, an attempt was made to start the volume volume specifying the access mode, but the volume volume is already active in an access mode other than the specified mode.
Resolution
Stop the volume volume and restart it as needed.
ERROR: volume: related to proxy volume proxy
Explanation
Volume volume is a master volume related to proxy volume proxy.
Resolution
Cancel the relationship of master volume volume and proxy volume proxy according to need and execute again.
ERROR: volume: related to master volume master
Explanation
Volume volume is a proxy volume related to master volume master.
Resolution
Cancel the relationship of master volume master and proxy volume volume according to need and execute again.
ERROR: volume: related to proxy volume proxy with EC
Explanation
EC session exists between volume volume and proxy volume proxy.
Resolution
Cancel the relationship of master volume volume and proxy volume proxy according to need, and execute again.
ERROR: volume: related to master volume master with EC
Explanation
EC session exists between volume volume and master volume master.
Resolution
Use the sdxproxy Cancel command and cancel the EC session between master volume master and proxy volume volume according to need. Alternatively, as needed, cancel the relationship of master volume master and proxy volume volume, and execute again.
ERROR: volume: related to proxy volume proxy with TimeFinder
Explanation
There is a BCV pair between the volume volume and the proxy volume proxy.
Resolution
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
ERROR: volume: related to master volume master with TimeFinder
Explanation
There is a BCV pair between the volume volume and the master volume master.
Resolution
Break the relation between the master volume master and the proxy volume volume according to need, and try the command again.
ERROR: volume: related to proxy volume proxy with SRDF
Explanation
There is an SRDF pair between the volume volume and the proxy volume proxy.
Resolution
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
ERROR: volume: related to master volume master with SRDF
Explanation
There is an SRDF pair between the volume volume and the master volume master.
Resolution
Break the relation between the master volume master and the proxy volume volume according to need, and try the command again.
ERROR: proxy : no parted proxy volume in proxy group
Explanation
No parted proxy volume exists in proxy group proxy.
Resolution
According to need, part the proxy and retry the command.
ERROR: volume: parted proxy volume
Explanation
Volume volume is a proxy volume parted from master volume.
Resolution
Rejoin the proxy volume to the master volume or break the relationship between them according to need and try this command again.
ERROR: group: related to proxy group proxy
Explanation
Group group is a master group related to proxy group proxy.
Resolution
Cancel the relationship between master group group and proxy group proxy according to need, and execute again.
ERROR: group: related to master group master
Explanation
Group group is a proxy group related to master group master.
Resolution
Cancel the relationship between master group master and proxy group group according to need, and execute again.
ERROR: volume: related to master or proxy volume
Explanation
Volume volume is related to either master volume or proxy volume.
Resolution
Cancel the relationship between master and proxy according to need, and execute again.
ERROR: volume: joined to master volume master
Explanation
Volume volume is a proxy volume joined to master volume master.
Resolution
Part volume volume from master volume master, or cancel the relationship with master volume according to need, and execute again.
ERROR: volume: copying from master volume master
Explanation
Data is being copied from master volume master to volume volume.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying from proxy volume proxy
Explanation
Data is being copied from proxy volume proxy to volume volume.
Resolution
After the copying process is complete, execute again.
ERROR: class is root class
Explanation
The class class is the root class. The attempted operation is not supported for the root class.
Resolution
Specify a correct class name.
ERROR: object: not volume nor group
Explanation
The object object is neither a volume nor a group.
Resolution
Check the GDS configuration and specify the correct volume name or group name. Execute again.
ERROR: different types of objects, master=master, proxy=proxy
Explanation
Different types of objects master and proxy were specified as the master and proxy.
Resolution
As the master and proxy, specify one of the following combinations.
Two volumes of the same type
A mirror volume and a single volume
Two mirror groups
For details, see "D.14 sdxproxy - Proxy object operations."
ERROR: object: same name as master
Explanation
The object name specified for proxy is the same as the master's name, object.
Resolution
Different object names must be specified for master and proxy.
ERROR: group: not a mirror group
Explanation
Group group is not a mirror group.
Resolution
Specify a correct group name.
ERROR: no volume exists in group
Explanation
There are no volumes in group group.
Resolution
Use sdxvolume -M command to create a volume within group group, and execute again.
ERROR: too many proxy volumes are related to master
Explanation
There are too many proxy volumes related to master object master.
Resolution
Check the GDS configuration.
For details about the number of proxy volumes, see "A.1.9 Number of Proxy Volumes."
ERROR: master: corresponding proxy volume name must be specified
Explanation
There is no corresponding proxy volume name specified for master volume master.
Resolution
ERROR: proxy: proxy volume name duplicated
Explanation
The same proxy volume name proxy is specified for more than one master volume.
Resolution
Specify a different name, and execute again.
ERROR: volume: no such volume in group
Explanation
Volume volume does not exist in group group.
Resolution
Specify a correct volume name or group name, and execute again.
ERROR: object: object name duplicated
Explanation
The duplicate object name object was specified, or the group to which the volume object belongs and the volume object itself were specified at the same time.
Resolution
You can specify an object only once.
ERROR: proxy: already parted
Explanation
Proxy volume proxy is already parted.
Resolution
Nothing needs to be done.
ERROR: one point copy not availableExplanation
The OPC (One Point Copy) function is unavailable and proxy operations cannot be performed.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "F.1.7 Proxy Object Abnormality."
ERROR: proxy: already joined
Explanation
Proxy object proxy is already joined.
Resolution
Nothing needs to be done.
ERROR: proxy: not joined to master
Explanation
Proxy volume proxy is not joined to master volume.
Resolution
Join the proxy volume proxy to master volume according to need, and execute again.
ERROR: proxy: no such proxy object
Explanation
Proxy object proxy cannot be found.
Resolution
Specify a correct proxy object name.
ERROR: master: no such master object
Explanation
Master object master cannot be found.
Resolution
Specify a correct master object name.
ERROR: volume: exists in proxy group
Explanation
Volume volume is a proxy volume in proxy group.
Resolution
Specify a proxy group and execute again.
ERROR: group: not a proxy group
Explanation
group is not a proxy group group name.
Resolution
Check the GDS configuration, and specify a proxy group group name.
ERROR: volume: copying with EC
Explanation
Volume volume is in the process of EC copy.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying with OPC
Explanation
Volume volume is in the process of OPC copy.
Resolution
After the copying process is complete, execute again.
ERROR: volume: copying with TimeFinder
Explanation
Volume volume is being copied with TimeFinder.
Resolution
Execute the command again after the copying process is complete.
ERROR: volume: copying with SRDF
Explanation
Volume volume is being copied with SRDF.
Resolution
Execute the command again after the copying process is complete.
ERROR: volume: related to same master volume as proxy proxy, master=master
Explanation
Volume volume is related to the same master volume master as proxy volume proxy.
Resolution
Specify a correct volume name. For details, see "Appendix D Command Reference."
ERROR: master and proxy exist in same group group
Explanation
The specified master volume and proxy volume exist in the same group group.
Resolution
Specify volumes that exist in different groups.
ERROR: proxy: joined to master with EC, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped since EC session in process between proxy proxy and master.
Resolution
Cancel the EC session by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: proxy: joined to master with TimeFinder, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped because there is a BCV pair between the proxy proxy and the master.
Resolution
Cancel the BCV pair by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: proxy: joined to master with SRDF, rejoin them by soft copy and try again
Explanation
Slices cannot be swapped because there is an SRDF pair between the proxy proxy and the master.
Resolution
Cancel the SRDF pair by either of the following operations according to need and try this command again.
Part the master and the proxy once and rejoin them with the sdxproxy Rejoin -e softcopy command.
Break the relationship between the master and the proxy once and rejoin them with the sdxproxy Join -e softcopy command.
ERROR: volume: proxy volume cannot be specified when using TimeFinder
Explanation
You cannot specify volume when you perform parting, rejoining or restoring because there is a BCV pair between the proxy volume volume and the master.
Resolution
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
ERROR: volume: proxy volume cannot be specified when using SRDF
Explanation
You cannot specify volume when you perform parting, rejoining or restoring because there is an SRDF pair between the proxy volume volume and the master.
Resolution
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
ERROR: proxy: failed to start soft copy
Explanation
An error occurred when synchronization copying with the soft copy function was started between the proxy volume proxy and the master volume.
Resolution
Collect investigation material and contact field engineers.
ERROR: OPC not availableExplanation
The OPC function is unavailable.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "F.1.7 Proxy Object Abnormality."
ERROR: EC not availableExplanation
The EC function is unavailable.
Resolution
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "F.1.7 Proxy Object Abnormality."
ERROR: proxy: too many EC/OPC sessions
Explanation
The number of EC or OPC sessions within the physical disk (LU) or the disk array body has reached the upper limit of supported concurrent sessions. For this reason, a new EC or OPC session cannot be started.
Resolution
To make copying by EC or OPC available, wait until the running session ends, and try this command again. Alternatively, according to need, cancel the running session using the sdxproxy Cancel command, the sdxproxy Break command, or [Operation]:[Proxy Operation]:[Break] and try this command again.
ERROR: proxy: offset is different from master volume master
Explanation
Master volume master and proxy volume proxy have different start block (sector) numbers. The start block number is not a physical block number that indicates the offset on a physical disk, but is a logical block number that indicates the offset within a group (or a single disk) to which the volume belongs.
Resolution
To relate a pair of of mirror groups, as the proxy group, specify a group whose volume layout is consistent with the master group's.
To relate a pair of stripe or concatenation volumes, as the proxy volume, specify a volume whose offset and size within the group are consistent with the master volume's. For the start block (sector) numbers and the sizes of volumes, use the sdxinfo command and check the 1STBLK field and the BLOCKS field of the displayed volume information.
ERROR: proxy: number of volumes is different from master group master
Explanation
Master group master and proxy group proxy include different numbers of volumes. The layout (offsets and sizes) of volumes within a master group and a proxy group must be consistent.
Resolution
For the proxy group, choose a group in which the layout of volumes is consistent with those of the master group.
ERROR: proxy: failed to start OPC, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between the proxy volume proxy and the master volume when OPC started.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates the class to which the copy source and the copy destination slices belong.
Resolution
Identify the cause by referring to GDS log messages, disk driver log messages, and ETERNUS Disk storage system log messages that were output right before the error occurrence, and recover the status.
ERROR: proxy: failed to start EC session, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between the proxy volume proxy and the master volume when the EC session started.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates the class to which the copy source and the copy destination slices belong.
Resolution
Identify the cause by referring to GDS log messages, disk driver log messages, and ETERNUS Disk storage system log messages that were output right before the error occurrence, and recover the status.
ERROR: copy region exceeds volume region, volume=volume, offset=blkno, size=size
Explanation
The region specified with the start block number blkno and the size size exceeds the region of the volume volume.
Resolution
Check the size of the volume volume using the sdxinfo command, and modify the copy region file.
ERROR: cannot open copy region file region_file, errno=errno
Explanation
Opening the copy region file region_file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: cannot read copy region file region_file, errno=errno
Explanation
Reading the copy region file region_file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: syntax error in copy region file region_file, line=line
Explanation
The copy region file region_file contains an error at the line indicated by line.
Resolution
Check contents of region_file.
ERROR: too many copy regions in copy region file region_file
Explanation
The copy region file region_file specifies too many copy regions.
Resolution
Modify region_file.
ERROR: copy region file region_file contains overlapping regions, line=line1, line=line2
Explanation
Copy regions file region_file specified in the lines indicated by line1 and line2 overlap.
Resolution
Check contents of region_file.
ERROR: OPC not available with multiple extentsExplanation
The disk unit may not support the OPC copy function with multiple extents or the function may not currently be available for some reason.
Resolution
Check the disk unit's hardware configuration. According to need, specify one copy region at a time and execute the command for every region.
ERROR: cannot get configuration information, sdxinfo(1) command failed
Explanation
The sdxinfo(1) command failed, and GDS configuration information could not be obtained.
Resolution
Remove the error after identifying the cause by referring to the message for the sdxinfo(1) command that was output right before the occurrence of the error, and try the sdxproxy Root command again.
ERROR: volume: alternative volume altvol already specified for volume curvol
Explanation
Another alternative volume volume was assigned to the volume curvol for which the alternative volume altvol has already been specified.
Resolution
You can specify only one alternative volume for a volume.
ERROR: volume: corresponding volume not specified in /etc/vfstab
Explanation
The volume volume is not the alternative volume of a volume described in /etc/vfstab as a file system or a swap area.
Resolution
Specify a volume that fits one of the following requirements.
Proxy volume of a master volume described in the /etc/vfstab file
Master volume of a proxy volume described in the /etc/vfstab file
Another proxy volume related to the master volume of a proxy volume described in the /etc/vfstab file
ERROR: volume: read only volume
Explanation
The access mode of the volume volume is ro (read only). Since a read-only volume cannot be mounted, this cannot be configured for an alternative boot environment.
Resolution
Change the access mode attribute of the volume volume to rw (read and write) using the sdxattr -V command, and try this command again.
ERROR: alternative root volume must be specifiedExplanation
The alternative root volume has not been specified.
Resolution
You must specify the alternative root volume.
ERROR: volume: file system cannot be checked or repaired, fsck(1M) command failed, exit-status=exitstat
Explanation
The fsck(1M) command for the volume volume failed, and a file system on volume could not be inspected or repaired.
The exit status of the fsck(1M) command is exitstat. Inconsistency may have arisen in the file system on volume.
Resolution
Remove the error after identifying the cause by referring to the message for the fsck(1M) command that was output right before the occurrence of the error and to the manual for the fsck(1M) command. If required, restore the data on volume, for example, using the backed up data, and try the sdxproxy Root command again.
ERROR: volume: file system cannot be mounted, mount(1M) command failed, exit-status=exitstat
details
Explanation
The mount(1M) command for the volume volume failed, and the file system on volume could not be mounted.
The exit status of the mount(1M) command is exitstat. details is the error message for the mount(1M) command.
Resolution
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
ERROR: volume: cannot change boot-device parameter, eeprom(1M) command failed, exit-status=exitstat
details
Explanation
The eeprom(1M) command failed, and the boot-device parameter could not be changed to the device for the volume volume.
The exit status of the eeprom(1M) command is exitstat. details is the error message for the eeprom(1M) command.
Resolution
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
ERROR: volume: file system cannot be unmounted, umount(1M) command failed, exit-status=exitstat
details
Explanation
The umount(1M) command for the volume volume failed, and the file system on volume temporarily mounted could not be unmounted.
The exit status of the umount(1M) command is exitstat. details is the error message for the umount(1M) command.
Resolution
Remove the error after identifying the cause based on details, unmount volume, and try the sdxproxy Root command again.
ERROR: class: not a shadow class
Explanation
The class class is not a shadow class.
Resolution
See "Appendix D Command Reference," and specify a proper command name and class name.
ERROR: device: no configuration information
Explanation
Since no configuration information resides in the private slice on the physical disk device or no private slice exists on device, device cannot be registered with a shadow class.
The possible causes are as follows.
a) device is not registered with a class in another domain yet, and the private slice has not been copied from the SDX disk to device with the disk unit's copy function. In addition, the disk is not a disk previously removed from a class with the sdxconfig Remove -e keepid command.
b) device is already registered with a class in another domain, but has not been enabled.
c) The private slice has been copied from the SDX disk to device with the disk unit's copy function, but the copy source SDX disk has not been enabled.
Resolution
Check on the system configuration and so on, and identify which cause among a), b) and c) applies. If the cause is a), see "Appendix D Command Reference" and specify a correct command name and physical disk name. If it is b), restore device in another domain. If it is c), restore the copy source SDX disk.
ERROR: device: registered with illegal class in another domain
Explanation
While the physical disk device is already registered with a different class in another domain, registering it with the same shadow class was attempted.
Resolution
You should register a disk registered with the same class in another domain with one shadow class.
ERROR: device: disk: not same as disk name diskname in another domain
Explanation
The physical disk device is already registered as diskname with a class in another domain. It cannot be registered with a shadow class as disk that is another disk name.
Resolution
Specify the same disk name diskname as in another domain.
ERROR: device: private slice size not same as another disk in class
Explanation
Since the physical disk device has the private slice that is unequal in size compared to the private slices on other disks registered with the shadow class class, it cannot be registered with class.
Resolution
Check on the system configuration and so on, and specify a correct disk name and shadow class name.
ERROR: no license
Explanation
The command cannot be executed. The possible causes are as follows.
a) In a system where the FJSVsdxl package of GDS is not installed normally, the sdxconfig command was used.
b) In a system where the FJSVsdxsl package of GDS Snapshot is not installed normally, the sdxshadowdisk command was used.
Resolution
To use the sdxconfig command, install FJSVsdxl normally. To use the sdxshadowdisk command, install FJSVsdxsl normally.
ERROR: output file already existsExplanation
The specified output file is an existing file.
Resolution
Specify a nonexistent file name. To overwrite an existing file, use the -e update option.
ERROR: failed to create configuration fileExplanation
Configuration file creation failed.
Resolution
Check whether the specified path to the configuration file is correct.
ERROR: class: failed to get configuration information
Explanation
Acquisition of class configuration information failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: proxy: proxy volume exists in class
Explanation
Proxy volume proxy exists in class.
Resolution
Break the relationship of proxy volume proxy to the master as needed.
ERROR: group: switch group exists in class
Explanation
Class class includes switch group group. The attempted operation is not supported for classes that include switch groups.
Resolution
Delete the group as needed and re-execute the command.
ERROR: failed to output configuration table
Explanation
Sending the configuration table to standard output or to a configuration file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: input file not foundExplanation
The specified input file does not exist.
Resolution
Specify a correct file name.
ERROR: class : not same as class name name in configuration table
Explanation
The specified class name class is different from the class name name in the configuration table.
Resolution
Specify a correct class name, or change the class name in the configuration table to class with the sdxconfig Convert command.
ERROR: disk : no such disk in configuration table
Explanation
The configuration table does not contain disk disk.
Resolution
Specify a correct disk name.
ERROR: device : no such device in configuration table
Explanation
The configuration table does not contain physical disk device.
Resolution
Specify a correct physical disk name.
ERROR: group : no such group in configuration table
Explanation
The configuration table does not contain group group.
Resolution
Specify a correct group name.
ERROR: object : exists in type group in configuration table
Explanation
In the configuration table object that is a disk or a lower level group is connected to a type type group. Disks connected to concat or stripe type groups and lower level groups connected to stripe type groups cannot be removed from configuration tables.
Resolution
Specify a correct disk name or group name.
ERROR: at least one object must remain in configuration tableExplanation
Removing the specified objects from the configuration table will result in no object in the configuration table. A configuration table needs to contain a minimum of one object.
Resolution
Specify correct object names.
ERROR: object.volume is only valid slice in configuration table
Explanation
In the configuration table slice object.volume is an only valid slice that comprises mirror volume volume. For this reason, object that is a disk or a lower level group cannot be removed from the configuration table.
Resolution
Specify a correct disk name or group name.
ERROR: class : not a local class
Explanation
Class class is not a local class.
Resolution
Specify a local class.
ERROR: file name too longExplanation
The specified file name contains too many characters.
Resolution
Specify a correct file name.
ERROR: failed to open input file, errno=errno
Explanation
Input file open failed.
Resolution
Identify the cause based on the error number errno.
ERROR: configuration table corrupted, sdxfunc=sdxfunc, sdxerrno=sdxerrno
Explanation
Contents of the configuration table are invalid.
Resolution
Collect investigation material and contact field engineers.
ERROR: class : already exists
Explanation
Class class already exists.
Resolution
Change the class name in the configuration table with the sdxconfig Convert command and re-execute the command.
ERROR: class : already exists in another node
Explanation
Class class already exists in another node.
Resolution
Change the class name in the configuration file with the sdxconfig Convert command and re-execute the command.
ERROR: device : assigned to disk1 and disk2 in configuration table
Explanation
In the configuration table one physical disk device is assigned to disks disk1 and disk2.
Resolution
Change the physical disk assigned to disk1 or disk2 in the configuration table with the sdxconfig Convert command and re-execute the command.
ERROR: device : failed to get physical disk information
Explanation
Acquisition of geometry information, VTOC, or the device number of physical disk device failed.
Resolution
Check whether physical disk device is normally operating.
ERROR: device : size must be size blocks
Explanation
The physical disk device must have size blocks.
Resolution
Replace physical disk device with a physical disk that has size blocks. Alternatively, change physical disk device in the configuration table to another physical disk that has size blocks with the sdxconfig Convert command.
ERROR: device : private slice size must be size blocks
Explanation
The size of the private slice of physical disk device is different from that described in the configuration table and therefore the class object configuration cannot be restored. The private slice (slice 0) of device must have size blocks.
Resolution
Exchange physical disk device for a physical disk whose private slice (slice 0) size is size blocks. Alternatively, change physical disk device in the configuration table to another physical disk whose private slice size is size blocks with the sdxconfig Convert command.
ERROR: mismatch of class names in private slices on device1 and device2
Explanation
The class names of physical disks device1 and device2 stored in the private slices do not match and therefore device1 and device2 cannot be registered with one class.
Resolution
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
ERROR: device : mismatch of disk names, disk1 in private slice, disk2 in configuration table
Explanation
The disk name disk1 stored in the private slice does not match the disk name disk2 described in the configuration table and therefore physical disk device cannot be registered as disk disk2 with a class.
Resolution
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
ERROR: class : restoration based on configuration file failed
Explanation
Restoration of the class configuration based on configuration file file failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: class: some node trying to get class master privilege
Explanation
The current node or some other node is trying to obtain master privileges of shared class class.
Resolution
If necessary, try the command again after a while.
ERROR: class: class master not found
Explanation
The class master of shared class class is not found and no operation is possible for class.
Resolution
If necessary, try the command again after a while.
ERROR: failed to update NVRAM configuration parameter,parameter='param'
Explanation
Updating the parameter param value in device's NVRAM (nonvolatile memory) failed.
Resolution
Collect investigation material and contact field engineers.
ERROR: proxy: number of disks is different from master group master
Explanation
Between the group master to which the master volume belongs and the group proxy to which the proxy volume belongs, the number of disks is different.
Resolution
Confirm the type and number of disks of master, and as the proxy volume, specify a volume that belongs to a group whose type and the number of disks are consistent with master's. For the type and number of disks of groups, use the sdxinfo -G -e long command and check the TYPES field and the DISKS field.
ERROR: proxy: stripe width is different from master group master
Explanation
Between the stripe group master to which the master volume belongs and the stripe group proxy to which the proxy volume belongs, the stripe width is different.
Resolution
Confirm the stripe width of master, and as the proxy volume, specify a volume that belongs to a group whose stripe width is consistent with the master's. For the stripe width of groups, use the sdxinfo -G -e long command and check the WIDTH field.
ERROR: proxy: disk size is different from master group master
Explanation
Between the concatenation group master to which the master volume belongs and the concatenation group proxy to which the proxy volume belongs, the disk configuration (size and connection order) is different.
Resolution
Confirm the configuration (size and connection order) of disks connected to master, and as the proxy volume, specify a volume that belongs to a concatenation group whose configuration is consistent with the master's. For the names and connection order of disks connected to a concatenation group, use the sdxinfo -G command and check the DISKS field. For the size of disks, use the sdxinfo - D command and check the DEVBLKS field.
ERROR: group: lower group is connected
Explanation
To the group group to which the master volume or the proxy volume belongs, a lower level group is connected.
Resolution
Specify a volume that belongs to a group to which no lower level group is connected. Alternatively, change group into a configuration in which no lower level group is connected.
ERROR: option: cannot be specified for stripe nor concat object
Explanation
The command option option cannot be specified for stripe type and concatenation type objects.
Resolution
See "Appendix D Command Reference."
ERROR: device: device is MPxIO disabled
Explanation
MPxIO is disabled for the physical disk device.
If MPxIO is disabled for the following disks, the sdxdisk -M command and the sdxshadowdisk -M command will output this message and terminate with an error.
The internal disk of SPARC M12/M10
The internal disk of SPARC T4-4/T4-2/T4-1/T3-4/T3-2/T3-1
The disk of Expansion File Unit connected to a 6Gbps SAS card
Resolution
MPxIO should be enabled for the device. Register the disk with the class after enabling MPxIO.
ERROR: disk: cannot be operated by sdxswap command
Explanation
disk cannot be operated by the sdxswap command.
Resolution
Remove disk from the class, change the disk unit, and re-register the new disk with the class.
ERROR: device: failed to get information of physical device
Explanation
Failed to get the information of the specified physical disk.
Resolution
See if the multipath configuration of the physical disk is correct. If you still cannot determine the cause of the error, collect investigation material and contact field engineers.
ERROR: device: disk label is not matched with class class
disk label of class = class-label
disk label of device = device-label
Explanation
Neither registration and restoration of device nor restoration of class can be performed because the disk label type of a physical disk device (device-label) is different from that of a class class (class-label) described in the current class or the configuration table.
Resolution
Change the disk label of device to class-label type by using the format(1M) command, etc. and try again. If the specified class or device is wrong, specify a correct object name.
ERROR: device: EFI labeled disk cannot be specified for root class
Explanation
The disk label of a physical disk device is EFI type, so neither registration with a root class nor restoration can be performed.
Resolution
Change the disk label of device to VTOC type by using the format(1M) command, etc. and try again. If the class name or the specified device is wrong, specify a correct object name.
ERROR: device: VTOC labeled disk equal to or larger than 1TB not supported
Explanation
A physical disk device is a 1 TB or larger VTOC labeled disk, so neither registration and restoration of device nor restoration of a class can be performed.
Resolution
Change the disk label of device to EFI type by using the format(1M) command, etc. and try again. If the class name or the specified device is wrong, specify a correct object name.
ERROR: pslice: I/O hangup detected on node node
Explanation
On the node node, a hang of the I/O to the physical slice pslice is detected. The node is forcibly panicked.
This message is output on the system log.
Resolution
A disk fault or a non-response in the I/O route domain may have occurred.
Check that the physical disk is working correctly on the node node.
ERROR: class: same class id assigned to another class in scope
Explanation
The same class ID as the class ID of the class class is used in another class on the node to be added to the scope.
Resolution
Take the following steps to remove the class class, and after recovering the status, change the scope.
Back up the object configuration information of the class in which a node is added to the scope. (sdxconfig Backup command)
Stop the volume of the class in which a node is added to the scope. (sdxvolume -F command)
For the shared class, change the class in which a node is added to the scope to the local class. (sdxattr -C command)
Remove the object configuration information of the class in which a node is added to the scope. (sdxconfig Remove command)
Restore the object configuration information of the class in which a node is added to the scope. (sdxconfig Restore command)
Add a node to the scope in the restored local class. (sdxattr -C command)
ERROR: I/O monitor option is not installedExplanation
GDS I/O Monitor Option was not installed correctly.
Resolution
Install the I/O Monitor Option correctly when using the sdsdisk -M command or the sdxattr -C command to set up the I/O Response Time Assurance, or using the sdxinfo -I command to check the information of the I/O Times Response Assurance.
ERROR: class: cannot change iotimeout attribute value to on, concat or stripe group exist
Explanation
The iotimeout attribute of the class cannot be changed to on because concat and stripe type groups exist in the class class.
Resolution
Check if there is no mistake in the specified class name or the object configuration in the class class.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the object configuration in the class, change it to the correct configuration.
ERROR: class: cannot create concat or stripe group, iotimeout attribute value is on
Explanation
Concat and stripe type groups cannot be created because the iotimeout attribute in class class is on.
Resolution
Check if there is no mistake in the specified class name or the iotimeout attribute value.
If there is a mistake in the specified class name, specify the correct class name and execute again.
If there is a mistake in the iotime attribute value of the class, use the sdxattr command to change the iotimeout command to off.