| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.2 (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."
Executed command has a syntax error.
See the Fix Messages described later, or the "Command Reference."
Object name, file name or node identifier specified with string is too long.
Specify the proper name.
Object name object contains an invalid character letter.
You can only use alphanumeric characters, "-" (hyphen), and "_" (underscore) when specifying an object name.
Object name object starting with "-" (hyphen) or "_" (underscore) is invalid.
Specify an object name that starts with an alphanumeric character.
Physical disk name device is illegal.
See "Command Reference."
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 a correct command name and class name.
The same attribute has already been specified.
See "Command Reference."
The same attribute attribute has already been specified.
You can only specify an attribute once.
Attribute value value is invalid.
See "Command Reference."
If "pslice=off: invalid attribute value" is output, the possible cause is that the FJSVsdx-bas package of PRIMECLUSTER GDS may not be installed normally. If this is the cause, reinstall FJSVsdx-bas.
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.
A remote node was specified for a local class.
Specify the node identifier of the current node for a local class.
A remote node was specified for a root class.
Specify the node identifier of the current node for a local class.
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 device has not been registered with the cluster resource database.
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 resource registration to register device with the resource database, 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 a 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 a correct physical disk.
There is no physical disk device.
Specify a correct physical disk name.
The physical disk device that composes the object object was not found.
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.
The physical disk device was not found.
The physical disk device may be connected incorrectly or a disk failure may have occurred. Fix device connection or recover from disk failure.
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.
device is already registered with another class.
device is registered with a class in another domain.
The entire SDX disk was copied or is being copied to device with the disk unit's copy function.
After registering device with the class, it was not removed normally, and the private slice and configuration information remain existent in device illegally.
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), collect investigation material and contact your local customer support.
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 "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 "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."
Keep disk cannot be registered with local or shared class.
Register keep disk with root class.
The number of specified keep disks exceeds that of undefined disks.
When registering multiple keep disks, specify the same number or more as undefined disks at the same time.
You tried to create a new class when there is already a root class. You can only create one root class within a node.
Specify the existing root class or a local class.
The physical disk device contains physical slices with overlapping cylinders.
Correct the physical slice configuration using the parted(8) command.
The physical disk device has no free slice number (number not assigned to a slice).
Change the physical slice configuration using the parted(8) command.
The physical disk device does not have sufficient free disk space.
Use the parted(8) command and create sufficient free disk space. For the size, see "Disk Size."
The physical disk device does not have free disk space or swap area.
Use the parted(8) command and create sufficient free disk space or swap area. For the size, see "Disk Size."
Physical disk device does not have sufficient free disk space or swap area.
Use the parted(8) command and create sufficient free disk space or swap area. For the size see "Disk Size."
Specified physical disk is managed by driver, and is therefore invalid.
Confirm the I/O and cluster system configuration, and specify a 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.
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.
Specify a shared class of which scope is 2 nodes.
Class class includes disk disk of the type type. The attempted operation is not supported for classes that include type type disks.
Delete disk from class as needed and re-execute the command.
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
Specify a correct class name.
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 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.
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 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.
The physical scope of inactive disk disk can include only node node.
Specify a correct 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 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.
There is no disk.
Check GDS configuration.
Disk or group indicated by object, is already connected to group group.
Specify a 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.
The specified physical slice number pslice_num is invalid.
For the physical slice number pslice_num, specify an integer from 1 to 15.
Physical slice pslice is a private slice.
If this message is output at the time of sdxdisk -M command execution, check whether the disk to which the physical slice pslice belongs is registered with a class in another domain. If it is registered, the disk cannot be registered with a class. If not, to register the disk to a class, it is necessary to delete the physical slice pslice, for example, with the parted(8) command.
If this message is output at the time of sdxdisk -C command execution, re-execute the sdxdisk -C command. When re-executing, do not specify the slice number of the physical slice pslice for the -v option.
Volume attributes corresponding to physical slice pslice is not specified.
See "Command Reference."
Object size of object is invalid.
See "Command Reference."
More than one keep disk cannot be connected to group.
See "Command Reference."
More than one single disk cannot be connected to a group.
See "Command Reference."
Both keep and single disks cannot be connected to a group at the same time.
See "Command Reference."
Keep disk disk cannot be connected to an existing group.
See "Command Reference."
Single disk disk cannot be connected to the existing group.
See "Command Reference."
More than one IDE disk cannot be connected to a group.
When mirroring an IDE disk, use it with disks other than IDE disks.
If the FJSVsdx-bas package of PRIMECLUSTER GDS is not installed, multiple disks cannot be connected to a group.
If FJSVsdx-bas has not been installed successfully, reinstall it.
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.
Specify a correct higher level group name.
Disk disk cannot be booted.
Confirm the disk configuration. When you cannot specify the cause, collect investigation material and contact your local customer support.
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 "Command Reference."
Since group lgroup is a mirror group, it cannot be connected to another group.
Specify a correct lower level group name.
Since the type attributes for group lgroup and higher level group hgroup are the same, lgroup cannot be connected to hgroup.
Specify a correct group name.
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.
Specify a correct group name.
The group group is a concatenation group connected to another group. Any group cannot be connected to group.
Disconnect group from the higher level group as needed and re-execute the command.
The group lgroup is a stripe group and cannot be connected to a concatenation group.
Specify a correct group name.
The group lgroup is a switch group and cannot be connected to a mirror group.
Specify a correct group name.
The group lgroup is a switch group and cannot be connected to a stripe group.
Specify a correct group name.
A disk is already connected to concatenation group hgroup, and a switch group cannot be connected.
Specify a correct group name.
size must be a positive integer.
Specify the correct size.
The indicated size size is invalid.
See "Command Reference."
There is no group.
Specify a 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, that is a class, a group, or a single disk.
Create volumes in another group or on a single disk as needed.
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.
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.
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:
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.
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 a correct disk name.
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 a correct disk name and 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.
Command option option cannot be specified for a root nor local class.
See "Command Reference."
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 a 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 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.
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.
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.
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "Online Volume Expansion."
volume cannot be resized since it is a volume created in a concatenation group.
See "Stripe Type Volume and Concatenation Type Volume Expansion" in "Online Volume Expansion."
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.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.
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.
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.
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.
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.
Disk space of disk or lower switch group object is assigned to volume volume, and object cannot be disconnected from the concatenation group.
If needed, remove volume first.
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.
Disk disk is the active disk of a lower level switch group, and physical disk swapping cannot be performed.
As needed, switch the active disk with the sdxattr -G command, and perform physical disk swapping on the previous active disk.
Group lgroup is not connected to group hgroup.
Specify a 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 a correct disk name.
You cannot specify slice by combining disk or group indicated by object, and volume indicated by volume.
See "Command Reference" and specify a correct disk or group name and volume name.
Volume is a single volume. Slices of single volumes cannot be detached.
Specify a correct volume name.
Volume volume is not a mirror volume.
Specify a correct volume name.
Disk or group indicated by object is not connected to the highest-level group.
See "Command Reference" and specify a 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.
Keep disk disk cannot be swapped.
Change the type attribute of disk, and execute the command again.
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.
Disconnect disk from the group, and execute the command in a situation where it is not connected to any group.
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 execute the command again.
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 a 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 a 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 "Command Reference" and specify a correct disk or group name and 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.
Class class is not closed. Recovery class with the sdxfix -C command is not required.
There is no resolution.
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.
See "Class Status Abnormality."
During recovery of class class from the closed status, class was closed on all the nodes within the class scope.
Re-execute the sdxfix -C command.
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.
The root class type attribute cannot be changed.
Specify a correct class name.
Class class with the same name as class already exists within the cluster domain.
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 "Changing Over from Single Nodes to a Cluster System [Linux2.6]."
A volume with the same minor number as that of a volume in the class class was found within the cluster domain.
See "Important Point 2" in "Changing Over from Single Nodes to a Cluster System [Linux2.6]."
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 resource registration. For the resource registration, see "Shared Disk Unit Resource Registration."
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 a 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.
Class class is not a root class.
The possible causes are as follows.
The specified class name is wrong.
An attempt to use a function that is only for a root class was made for a local class or a shared class.
In a system where the FJSVsdx-bas package of PRIMECLUSTER GDS is not installed normally, an attempt to create a local class group or a shared class group was made.
In a system where the FJSVsdx-bss package of PRIMECLUSTER GDS Snapshot is not installed normally, an attempt to perform proxy operation was made for a local class or a shared class.
If the cause is a) or b), see "Command Reference" and specify a correct class name. If it is c) or d), install FJSVsdx-bas or FJSVsdx-bss normally.
Disk disk is not a keep disk.
See "Command Reference" and specify a correct disk name.
Disk disk is not connected to a group.
See "Command Reference" and specify a correct disk name.
There is volume in status status in group.
Recover volume status, and execute the command again.
Disk disk is not a system disk.
Specify a correct disk name, and execute the command again.
he system disk device is not registered with the class class. device contains the slice currently operating as / (root), /usr, /var, /boot, or /boot/efi, and to perform system disk setting, it is necessary to register device with class.
Complete preparations properly referring to "System Disk Settings [Itanium]" or "Command Reference" and execute the command again.
The system disk disk was not specified. disk contains the slice currently operating as / (root), /usr, /var, /boot, or /boot/efi, and to cancel disk mirroring, it is necessary to specify disk.
Specify all system disks with the slices currently operating as / (root), /usr, /var, /boot, or /boot/efi, and execute the command again.
group to which disk is connected has two or more disks connected.
See "Command Reference" and complete preparation correctly. Then execute the command again.
Root file system is not mounted on volume.
Confirm the configuration, and see "Command Reference."
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.
class is not a shared class.
Specify a shared class.
Paramater name param is invalid.
See "Command Reference."
Parameter value val is invalid
See "Command Reference."
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 "Command Reference."
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.
There is a BCV pair between the volume volume and the proxy volume proxy.
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
There is a BCV pair between the volume volume and the master volume master.
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command again.
There is an SRDF pair between the volume volume and the proxy volume proxy.
Break the relation between the master volume master and the proxy volume volume according to need, and try the command again.
There is an SRDF pair between the volume volume and the master volume master.
Break the relation between the master volume volume and the proxy volume proxy according to need, and try the command 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.
The class class is the root class. The attempted operation is not supported for the root class.
Specify a correct class name.
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.
Specify a correct group name.
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 "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 a 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.
The OPC (One Point Copy) function is unavailable and proxy operations cannot be performed.
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "Proxy Object Abnormality."
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 a correct proxy object name.
Master object master cannot be found.
Specify a 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 being copyed with TimeFinder.
Execute the command again after the copying process is complete.
Volume volume is being copied with SRDF.
Execute the command again after the copying process is complete.
Volume volume is related to the same master volume master as proxy volume proxy.
Specify a 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.
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.
Slices cannot be swapped because there is a BCV pair between the proxy proxy and the master.
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.
Slices cannot be swapped because there is an SRDF pair between the proxy proxy and the master.
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.
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.
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
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.
If you wish to perform parting, rejoining, or restoring, you must specify the group to which volume belongs when executing the command.
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.
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "Proxy Object Abnormality."
The EC function is unavailable.
See "(1) The Advanced Copy function cannot be used in master-proxy copying." in "Proxy Object Abnormality."
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.
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.
Identify the cause by referring to GDS log messages, disk driver log messages, and Fujitsu Storage Systems ETERNUS log messages that were output right before the error occurrence, and recover the status.
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.
Identify the cause by referring to GDS log messages, disk driver log messages, and Fujitsu Storage Systems ETERNUS log messages that were output right before the error occurrence, and recover the status.
The region specified with the start block number blkno and the size size exceeds the region of the volume volume.
Check the size of the volume volume using the sdxinfo command, and modify the copy region file.
Opening the copy region file region_file failed.
Collect investigation material and contact your local customer support.
Reading the copy region file region_file failed.
Collect investigation material and contact your local customer support.
The copy region file region_file contains an error at the line indicated by line.
Check contents of region_file.
The copy region file region_file specifies too many copy regions.
Modify region_file.
Copy regions specified in the lines indicated by line1and line2 overlap.
Check contents of region_file.
The disk unit may not support the OPC copy function with multiple extents or the function may not currently be available for some reason.
Check the disk unit's hardware configuration. According to need, specify one copy region at a time and execute the command for every region.
The sdxinfo(1) command failed, and GDS configuration information could not be obtained.
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.
Another alternative volume volume was assigned to the volume curvol for which the alternative volume altvol has already been specified.
You can specify only one alternative volume for a volume.
The volume volume is not the alternative volume of a volume described in /etc/fstab as a file system or a swap area.
Specify a volume that fits one of the following requirements.
Proxy volume of a master volume described in the /etc/fstab file
Master volume of a proxy volume described in the /etc/fstab file
Another proxy volume related to the master volume of a proxy volume described in the /etc/fstab file
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.
Change the access mode attribute of the volume volume to rw (read and write) using the sdxattr -V command, and try this command again.
The alternative root volume has not been specified.
You must specify the alternative root volume.
The fsck(8) command for the volume volume failed, and a file system on volume could not be inspected or repaired. The exit status of the fsck(8) command is exitstat. Inconsistency may have arisen in the file system on volume.
Remove the error after identifying the cause by referring to the message for the fsck(8) command that was output right before the occurrence of the error and to the manual for the fsck(8) command. If required, restore the data on volume, for example, using the backed up data, and try the sdxproxy Root command again.
details
The mount(8) command for the volume volume failed, and the file system on volume could not be mounted. The exit status of the mount(8) command is exitstat. details is the error message for the mount(8) command.
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
details
The efibootmgr(8) command failed and the boot manager setting to boot from the volume volume was not set. The exit status of the efibootmgr(8) command is exitstat. details is the error message for the efibootmgr(8) command.
Remove the error after identifying the cause based on details, and try the sdxproxy Root command again.
details
The umount(8) command for the volume volume failed, and the file system on volume temporarily mounted could not be unmounted. The exit status of the umount(8) command is exitstat. details is the error message for the umount(8) command.
Remove the error after identifying the cause based on details, unmount volume, and try the sdxproxy Root command again.
The class class is not a shadow class.
See "Command Reference," and specify a 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 possible causes are as follows.
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.
device is already registered with a class in another domain, but has not been enabled.
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.
Check on the system configuration and so on, and identify which cause among a), b) and c) applies. If the cause is a), see "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.
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 a correct 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 command cannot be executed. The possible causes are as follows.
In a system where the FJSVsdx-cmd package of PRIMECLUSTER GDS is not installed normally, the sdxconfig command was used.
In a system where the FJSVsdx-ss package of PRIMECLUSTER GDS Snapshot is not installed normally, the sdxshadowdisk command was used.
To use the sdxconfig command, install FJSVsdx-cmd normally. To use the sdxshadowdisk command, install FJSVsdx-ss normally.
The specified output file is an existing file.
Specify a nonexistent file name. To overwrite an existing file, use the -e update option.
Configuration file creation failed.
Check whether the specified path to the configuration file is correct.
Acquisition of class configuration information failed.
Collect investigation material and contact your local customer support.
Proxy volume proxy exists in class.
Break the relationship of proxy volume proxy to the master as needed.
Class class includes switch group group.
The attempted operation is not supported for classes that include switch groups.
Delete the group as needed and re-execute the command.
Sending the configuration table to standard output or to a configuration file failed.
Collect investigation material and contact your local customer support.
The specified input file does not exist.
Specify a correct file name.
The specified class name class is different from the class name name in the configuration table.
Specify a correct class name, or change the class name in the configuration table to class with the sdxconfig Convert command.
The configuration table does not contain disk disk.
Specify a correct disk name.
The configuration table does not contain physical disk device.
Specify a correct physical disk name.
The configuration table does not contain group group.
Specify a correct group name.
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.
Specify a correct disk name or group name.
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.
Specify correct object names.
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.
Specify a correct disk name or group name.
Class class is not a local class.
Specify a local class.
The specified file name contains too many characters.
Specify a correct file name.
Input file open failed.
Identify the cause based on the error number errno.
Contents of the configuration table are invalid.
Collect investigation material and contact your local customer support.
Class class already exists.
Change the class name in the configuration table with the sdxconfig Convert command and re-execute the command.
Class class already exists in another node.
Change the class name in the configuration file with the sdxconfig Convert command and re-execute the command.
In the configuration table one physical disk device is assigned to disks disk1 and disk2.
Change the physical disk assigned to disk1 or disk2 in the configuration table with the sdxconfig Convert command and re-execute the command.
Acquisition of geometry information, partition table, or the device number of physical disk device failed.
Check whether physical disk device is normally operating.
The physical disk device must have size blocks.
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.
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 of device must have size blocks.
Exchange physical disk device for a physical disk whose private slice 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.
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.
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
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.
Check the system configuration and edit the physical disks described in the configuration table with the sdxconfig Convert command.
Restoration of the class configuration based on configuration file file failed.
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
|