| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Linux) |
|
Contents
|
| Appendix E GDS Messages | > E.4 Command Messages |
Connection failed due to no response from sdxservd daemon.
Confirm that sdxservd daemon process was started normally.
Executed user is not a superuser.
You need to have superuser authority for execution.
option is illegal.
See the Fix Messages described later, or the "Command Reference " in the manual.
Executed command has a syntax error.
See the Fix Messages described later, or the "Command Reference " in the manual.
Object name, file name or node identifier specified with string is too long.
Specify the proper object name or node identifier.
Object name object contains an invalid character letter.
You can only use alphanumeric characters, -(hyphen), and _(underscore) when specifying an object name.
Object name starting with "-" (hyphen) or "_" (underscore) is invalid.
Specify an object name that starts with an alphanumeric character.
Physical disk name device is illegal.
See the "Command Reference" in the manual
Object names within a class must be unique.
Specify a unique object name.
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.
Collect investigation material and contact your local customer support.
The class class is a shadow class. The attempted operation is not supported for shadow classes.
See "Command Reference," and specify the proper command name and class name.
The same attribute has already been specified.
See the "Command Reference" in the manual
The same attribute attribute has already been specified.
You can only specify an attribute once.
Attribute value value is invalid.
See the "Command Reference" in the manual.
The same node identifier has already been specified.
You can only specify a node identifier once.
There are too many nodes specified in scope.
Up to 4 nodes can be specified in a scope.
Cannot operate shared object since cluster control is not operating.
Start cluster control and try again.
Current node is not specified for shared class scope.
Always specify a node set which includes current node as scope.
Only one node is specified for shared class scope.
Multiple node identifiers must be specified in a scope.
Node node does not exist.
First check the cluster system environment. Then, try again after changing the node identifier.
Scope of class does not include the current node.
In the cluster system, class created in another node is specified.
Execute command on a node sharing class. Or, change the specified class name.
Current node node is a standby node in shared class class.
Execute the command from another active node.
There are too many disks registered with class.
Create a new class.
The physical disk device has not been connected to the node node, or registration of the cluster resources is not completed properly.
Check the system configuration and the resource configuration. If device has not been connected to node, specify the proper physical device name and re-execute the command. If no disk resource exists, execute automatic resource registration of the cluster and re-execute the command.
Physical disk device is not a shared disk unit, or cluster shared disk definition may not be correct.
Check the system configuration and execute the command.
Physical disk device is already registered with class.
Same physical disk cannot be registered with more than one class. Specify the correct physical disk.
Physical disk device is already registered with another class. This class is not shared by current node.
Same physical disk cannot be registered with more than one class. Specify the correct physical disk.
There is no physical disk device.
Specify the correct physical disk name.
Cannot open physical disk device.
Confirm that physical disk device is operating normally.
Physical disk device is not a hard disk.
GDS cannot manage devices other than hard disks.
Physical disk unit with the driver name driver is not supported.
There is no resolution.
Physical disk device format is illegal.
Check the format status.
Object object is in use.
Change to unused status and execute the command again.
Object object is used in a cluster application.
Check the cluster environment settings.
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.
Check the system configuration and so on, and identify the cause among a) to d). If the cause is a) or b), there is no resolution. If it is c) or d), use the fdisk(8) command and remove the slice whose tag is 33 as needed.
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.
See the "Command Reference."
Class class includes a switch group and the type can only be set to "undef" for registering physical disk device to class.
See the "Command Reference."
A write error occurred in physical disk device.
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.
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.
Check the system configuration and so on, and specify a physical disk and class name properly.
Object name object already exists within class. You cannot create multiple objects with the same name.
Specify another name and execute the command again.
Connecting to sdxcld, a GDS cluster linked daemon was unsuccessful.
When unable to identify the cause, collect investigation material and contact your local customer support.
Physical disk driver returned an error.
Identify the cause by referring to error number and message log.
Operating special file was unsuccessful.
Identify the cause by referring to error number and GDS log message.
GDS driver returned an error.
Identify the cause by referring to error number, GDS log message, and syslog message.
GDS driver returned a temporary error.
Execute the command again after a while.
class is closed. You cannot operate objects within a 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 "Class Status Abnormality."
class is closed on another node. You cannot operate objects within a closed class.
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 "Class Status Abnormality."
Specified physical disk is managed by driver, and is therefore invalid.
Confirm the I/O and cluster system configuration, and specify the correct physical disk name.
The device is an IDE disk. It cannot be used as a spare disk.
For spare disks, use disks other than IDE disks.
Cannot find class.
Check GDS configuration.
group is not a group name.
There is another object with the name group within class. Check configuration.
Group group is a stripe group connected to another group. Disks and groups cannot be connected to or disconnected from group.
Disconnect group from the higher level group as necessary.
Group group is connected to a lower level stripe group. Disks and groups cannot be connected to or disconnected from group.
Disconnect the higher level stripe group of group from its higher level group as necessary.
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.
Create a new class.
The maximum number of disks or lower level groups are already connected to group group.
There is no resolution. With mirror groups, the maximum number of objects you can connect is eight. With stripe groups and concatenation groups, it is sixty-four.
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.
Either 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.
The scope of class class includes 3 or more nodes. Classes whose scope includes 3 or more nodes cannot include switch groups.
There is no resolution.
Class class includes disk disk of the type type. The attempted operation is not supported for classes that include type type disks.
There is no resolution.
Class class includes group group that is not a switch group, such as a mirror group, a concatenation group, or a stripe group. The attempted operation is not supported for classes that include such groups.
There is no resolution.
When creating a switch group, specify the active disk in the -a actdisk=disk option.
Specify the option properly, referring to "Command Reference."
Active disk disk was not specified in the -d option.
When creating a switch group, specify one of the disks specified in the -d option of the sdxdisk -C command as the active disk.
Too many disks specified.
Specify a proper number of disks. For the number of disks that can be connected to a group, see " Number of Disks."
The physical scope of disk disk is not included in the class scope and disk cannot be connected to a switch group.
Specify a proper 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.
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.
Specify a proper 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.
The physical scope of inactive disk disk can include only node node.
Specify a proper disk name, referring to "Command Reference."
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.
Specify a proper 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.
There is no disk.
Check GDS configuration.
Disk or group indicated by object, is already connected to group group.
Indicate the correct disk name or group name.
disk is a spare disk. You cannot connect a spare disk to a group.
Change the disk attributes to undefined, and execute the command again.
Object status is not status status.
Confirm that object status is status, and execute the command again.
The size of object is too small.
Check the necessary object size and specify a larger object.
You must connect another disk to group.
Connect another disk and execute the command again.
Invalid physical slice number pslice_num is specified.
For physical slice number pslice_num, specify an integer from 0 to 7, excluding 2.
Physical slice pslice is a private slice.
Do not specify a private slice for physical slice number.
Volume attributes corresponding to physical slice pslice is not specified.
See the "Command Reference" in the manual
Object size of object is invalid.
See the "Command Reference" in the manual
More than one single disk cannot be connected to a group.
See the "Command Reference" in the manual.
Single disk disk cannot be connected to the existing group.
See the "Command Reference" in the manual.
More than one IDE disk cannot be connected to a group.
When mirroring an IDE disk, use it with disks other than IDE disks.
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.
For details, see "Class Status Abnormality."
Group group does not have a disk in ENABLE status connected.
See "Disk Status Abnormality" and recover disks connected to the group.
Delay time msec is invalid.
See the "Command Reference" in the manual.
Since group lgroup is a mirror group, it cannot be connected to another group.
There is no resolution.
Since group hgroup is a concatenation group, any group cannot be connected to hgroup.
There is no resolution.
Since the type attributes for group lgroup and higher level group hgroup are the same, lgroup cannot be connected to hgroup.
There is no resolution.
For the higher level group name, name hgoup, which is the same as the lower level group was indicated.
Different names must be indicated for higher level group and lower level group.
Group hgroup is a switch group and any group cannot be connected to.
There is no resolution.
Group lgroup is a switch group and cannot be connected to any group.
There is no resolution.
size must be a positive integer.
Specify the correct size.
The indicated size size is invalid.
See the "Command Reference" in the manual.
There is no group.
Specify the correct group name.
Group group is not the highest level group.
Disconnect group from the higher level group as necessary.
The maximum number of volumes, already exists in the object object, that is a class, a group, or a single disk.
No resolution.
Although a physical slice cannot be created in group group, an attempt was made to create a volume with one or more physical slices.
Create a volume without any physical slice for group either by:
If group is a mirror group, connect one or more disks to the group in order to create a volume with a physical slice.
There is not enough space in the group or single disk indicated by object.
Change the size you specify as needed.
The disk disk is not a single disk.
Specify an appropriate disk.
disk in status status is connected to group.
Restore the status of disk and execute the command again.
The disk in status status is connected to group, or it connected to the lower level group of group.
Confirm the disk status, and please execute a command again after canceling the status status if necessary.
disk is not connected to group.
Specify the correct disk name or group name.
Disk disk (physical disk name is device ) is in use.
Change to unused status, and execute the command again.
Too many nodes were specified.
Specify the nodes included in the scope of the class.
Node node is not included in the scope of the class class.
Confirm your GDS configuration, specify a node included in the scope of the class, and try the command again.
Starting volume volume was unsuccessful due to the class to which volume belongs in closed status.
Recover the 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 "Class Status Abnormality."
There is no volume.
Specify the correct volume name.
object is in status status.
Confirm the object status, and cancel the status if necessary.
Volumes of class class are already active on node node, and volumes of class cannot be started or created on this node.
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.
Volumes of class class are already active on node node, and volume volume cannot be started on this node.
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.
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.
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.
The "Lock volume" mode for volume volume on node node is turned on.
Turn off the "Lock volume" mode, or use the -e unlock option as necessary.
Stopping volume volume was unsuccessful due to the class to which volume belongs being in closed status.
Recover the 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 "Class Status Abnormality."
Slice object.volume in status status exists in object.
Confirm the object status, and cancel the status if necessary.
object on node is in status status.
Confirm the object status, and cancel the status if necessary.
volume cannot be resized since it is a volume created in a stripe group.
There is no resolution.
volume cannot be resized since it is a volume created in a concatenation group.
There is no resolution.
The volume volume cannot be resized since it is a mirror volume that consists of multiple mirror slices.
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.
Spare disk is connected instead of disk.
First recover the disk status.
Object object is the only disk or group connected to the lower level group group. You cannot disconnect object from group.
Disconnect group from the higher level group as necessary.
Disk disk is not the disk that was concatenated last to the concatenation group group.
You cannot disconnect disk from group.
There is no resolution.
Area on disk disk is allocated to volume volume. You cannot disconnect disk from the concatenation group.
First remove volume if necessary.
Group group has a connected inactive disk and physical disk swapping or disconnection cannot be performed for the active disk of the group.
According to need, switch the active disk with the sdxattr -G command and perform physical disk swapping or disconnection for the previous active disk.
Group lgroup is not connected to group hgroup.
Indicate the correct group name.
One or more volumes exist in group group.
First, remove the volume if necessary.
disk is connected to group.
First, disconnect the disk from group if necessary.
When there is a disk in SWAP or DISABLE status in class, you cannot remove the last disk in ENABLE status.
First recover the disk in SWAP or DISABLE status. Or, you can register a new disk with class.
Disk disk stores the configuration database and removal of disk will result in class closure. For this reason, the disk cannot be removed.
Recover or remove a failed disk in the class that includes disk and then remove disk.
Volume exists in disk.
First, remove the volume as needed.
Group exists in class.
First, remove the group as needed.
disk in status status exists in class.
First, restore the disk in status status.
volume in status status on node exists in class.
First, change the volume status as needed.
There is no disk disk.
Specify the correct disk name.
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
See the "Command Reference" and indicate the correct disk name, group name or volume name.
The volume is a single volume. Slices of single volumes cannot be detached.
There is no resolution.
Volume volume is not a mirror volume.
There is no resolution.
Disk or group indicated by object is not connected to the highest-level group.
See the "Command Reference" and indicate the correct disk name or group name.
You cannot swap the last ENABLE status disk in class.
Depending on the configuration, use a different method to avoid such situations. For example, you can register a new disk with class.
There is a volume related to disk in status status.
First, recover the volume in status status.
The highest level group of disk disk is not a mirror group. You cannot swap disk.
There is no resolution.
Disk disk stores the configuration database and swapping disk will close down the class. Therefore, swapping the disk is prevented.
Replace a failed disk included in the class to which disk is registered and swap disk.
Disk disk (the physical disk name is device) is in use on node.
Change the status to unused and retry the command.
Cannot open physical disk device.
Confirm that physical disk device is operating normally.
Physical disk device is not a hard disk.
Specify a hard disk.
Physical disk device format is illegal.
Check the format of the physical disk.
Physical disk pslice is in use.
Change to unused status and execute the command again.
Physical disk device is used in a cluster application.
Check the settings for cluster environment.
Physical disk size is too small.
Specify a physical disk with sufficient size.
Physical disk device is not connected to node. Or, cluster shared disk definition may not be correct.
Check the system configuration and execute the command.
Specified disk (corresponding physical disk name is device) is managed by driver, and is therefore invalid.
Confirm the I/O and cluster system configuration, and specify the correct physical disk name.
Slice object.volume in status status already exists in group group.
Check the object status and cancel status status if necessary.
On node node, physical disk device of disk disk has been managed by driver driver and cannot be handled.
Check I/O configurations and cluster system configurations, and specify the correct physical disk name.
Physical disk device cannot be opened on node node.
Check whether or not the physical disk device is operating normally.
Physical disk device on node node is not a hard disk.
Specify a hard disk.
The format of physical disk device on node node is incorrect.
Check the format.
Physical disk pslice on node node is in use.
Change the status to unused and retry the command.
Physical disk device on node node is being used by cluster applications.
Check the cluster environment configurations.
The size of physical disk device on node node is too small.
Replace it with a physical disk of sufficient size.
A read error occurred on physical disk device.
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
A read error occurred on physical disk device on node node.
The possible cause is a disk failure. Identify the cause based on disk driver log messages and so on and restore the disk.
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.
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.
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
See the "Command Reference" and indicate the correct disk name, group name or volume name.
Disk disk is not the active disk.
Specify the active disk.
An I/O error has not been occured on the disk disk. There is no need to restore disk using the sdxfix -D command.
There is no resolution.
Disk disk is connected to a switch group and an I/O error status of the disk cannot be removed.
Make disk switchable 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.
Copying process within volume could not be resumed.
Cancel the interrupted copying process according to need and resume copying.
Class with the same name as class already exists within the cluster domain.
Specify another class name.
Disks that are not connected to node node or for which disk resources are not created yet exist in the class.
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 "Register shared disk units."
The disk is an IDE disk. It can not be used as a spare disk.
For spare disks, use disks other than IDE disks.
There is no object.
Specify the correct object name.
Share object information is not available yet.
Wait until cluster control is activated, and execute the command again.
You cannot proceed with operation since node is in stopped status.
Start the node and try again.
node is in an abnormal status and cannot proceed with operation.
Confirm the normal startup of node and try again.
Cannot proceed with operation since communication failed with cluster.
Check that the cluster system and GDS are operating normally.
After recovering, try again.
Cannot proceed with operation since communication failed with cluster.
Check that the cluster system and GDS are operating normally.
After recovering, try again.
Cluster communication with remote node node failed. Operation cannot be performed.
Check that the cluster system and GDS are operating normally.
After recovering, try again.
Disk disk is not connected to a group.
See the "Command Reference" in the manual and specify the correct disk name.
There is volume in status status in group.
Recover volume status, and execute the command again.
group to which disk is connected has two or more disks connected.
See the "Command Reference" and complete preparation correctly. Then execute the command again.
Slice name includes a "." (period).
Specify the correct slice name.
Slice disk.volume cannot be operated on the current node.
Take over the slice by executing sdxslice -T command.
The physical slice attribute value of volume volume is "off." A slice in a volume without physical slices cannot be detached.
Retry the command after turning the physical slice attribute of volume to be "on" according to need.
object is in use on node.
Change to unused status and execute the command again.
Paramater name param is invalid.
See the "Command Reference" in the manual.
Parameter value val is invalid
See the "Command Reference" in the manual.
The same parameter name param has already been specified.
You can only use a parameter name once.
Value smaller than the number of copying currently in process has been specified for copy_concurrency parameter.
Set a value more than or equal to the number of copying currently in process for copy_concurrency parameter.
Multiple access modes have been specified.
Specify only one access mode.
Access mode value string is invalid.
See the "Command Reference" in the manual.
sdxvolume -M command was executed with -e mode=val option on node node, but volume volume had already been started with a different access mode.
Stop volume volume according to need and execute again.
Volume volume is a master volume related to proxy volume proxy.
Cancel the relationship of master volume volume and proxy volume proxy according to need and execute again.
Volume volume is a proxy volume related to master volume master.
Cancel the relationship of master volume master and proxy volume volume according to need and execute again.
EC session exists between volume volume and proxy volume proxy.
Cancel the relationship of master volume volume and proxy volume proxy according to need, and execute again.
EC session exists between volume volume and master volume master.
Use the sdxproxyCancel command and cancel the EC session between master volume volume and proxy volume volume according to need. Alternatively, as needed, cancel the relationship of master volume volume and proxy volume volume, and execute again.
No parted proxy volume exists in proxy group proxy.
According to need, part the proxy and retry the command.
Volume volume is a proxy volume parted from master volume.
Rejoin the proxy volume to the master volume or break the relationship between them according to need and try this command again.
Group group is a master group related to proxy group proxy.
Cancel the relationship between master group group and proxy group proxy according to need, and execute again.
Group group is a proxy group related to master group master.
Cancel the relationship between master group master and proxy group group according to need, and execute again.
Volume volume is related to either master volume or proxy volume.
Cancel the relationship between master and proxy according to need, and execute again.
Volume volume is a proxy volume joined to master volume master.
Part volume volume from master volume master, or cancel the relationship with master volume according to need, and execute again.
Data is being copied from master volume master to volume volume.
After the copying process is complete, execute again.
Data is being copied from proxy volume proxy to volume volume.
After the copying process is complete, execute again.
Object object is neither a volume or a group.
Check the GDS configuration and specify the correct volume name or group name. Execute again.
Different types of objects were specified as master and proxy.
Specify a pair of volumes or groups as master and proxy.
The object name specified for proxy is the same as the master's name, object.
Different object names must be specified for master and proxy.
Group group is not a mirror group.
There is no resolution.
There are no volumes in group group.
Use sdxvolume -M command to create a volume within group group, and execute again.
There are too many proxy volumes related to master object master.
Check the GDS configuration. For details about the number of proxy volumes, see "Number of Proxy Volumes."
There is no corresponding proxy volume name specified for master volume master.
See the "sdxproxy - Proxy object operations."
The same proxy volume name proxy is specified for more than one master volume.
Specify a different name, and execute again.
Volume volume does not exist.
Specify the correct volume name or group name, and execute again.
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.
You can specify an object only once.
Proxy volume proxy is already parted.
Nothing needs to be done.
Instant snapshot cannot be created, since OPC (One Point Copy) function is not available.
Possible causes are as follows.
Check disk array unit settings and GDS object configurations and identify the cause. According to the cause, take one of the following actions.
Proxy object proxy is already joined.
Nothing needs to be done.
Proxy volume proxy is not joined to master volume.
Join the proxy volume proxy to master volume according to need, and execute again.
Proxy object proxy cannot be found.
Specify the correct proxy object name.
Master object master cannot be found.
Specify the correct master object name.
Volume volume is a proxy volume in proxy group.
Specify a proxy group and execute again.
group is not a proxy group group name.
Check the GDS configuration, and specify a proxy group group name.
Volume volume is in the process of EC copy.
After the copying process is complete, execute again.
Volume volume is in the process of OPC copy.
After the copying process is complete, execute again.
Volume volume is related to the same master volume master as proxy volume proxy.
Specify the correct volume name. For details, see "Command Reference."
The specified master volume and proxy volume exist in the same group group.
Specify volumes that exist in different groups.
Slices cannot be swapped since EC session in process between proxy proxy and master.
Cancel the EC session by either of the following operations according to need and try this command again.
An error occurred when synchronization copying with the soft copy function was started between the proxy volume proxy and the master volume.
Collect investigation material and contact your local customer support.
The OPC function is unavailable. Possible causes are as follows.
Check disk array unit settings and GDS object configurations and identify the cause. According to the cause, take one of the following actions.
The EC function is unavailable. Possible causes are as follows.
Check disk array unit settings and GDS object configurations and identify the cause. According to the cause, take one of the following actions.
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.
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.
Master volume master and proxy volume proxy have different top block (sector) numbers. The top 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. The layout (offsets and sizes) of volumes within a master group and a proxy group must be consistent.
For the proxy group, choose a group in which the layout of volumes are consistent with those of the master group. For the top 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.
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.
For the proxy group, choose a group in which the layout of volumes are consistent with those of the master group.
The class class is not a shadow class.
See "Command Reference," and specify the proper command name and class name.
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 cause of this error may be one of the following.
Check on the system configuration and so on, and identify which cause among a) and b) applies. If a) applies, see "Command Reference" and specify the proper command name and physical disk name. If b) applies, restore device in another domain.
While the physical disk device is already registered with a different class in another domain, registering it with the same shadow class was attempted.
You should register a disk registered with the same class in another domain with one shadow class.
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.
Specify the same disk name diskname as in another domain.
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.
Check on the system configuration and so on, and specify the proper disk name and shadow class name.
The device to be registered has been bound to a RAW device.
With GDS, you cannot register disks bound to a RAW device.
Register a disk not bound to a RAW device. Alternatively, cancel the bind to a RAW device using the raw(8) command and then register.
The environment has an error and the command cannot be executed. The command is inexecutable but there is no other influence on the system. Volumes can be continuously accessed without problems.
Collect investigation material and contact your local customer support.
The local node or some other node is trying to obtain master privileges of shared class class.
If necessary, try the command again after a while.
The class master of shared class class is not found and no operation is possible for class.
If necessary, try the command again after a while.
|
Contents
|