| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Linux) |
|
Contents
|
| Appendix E GDS Messages | > E.3 Daemon Messages |
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info: blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Read request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error. You must attempt recovery as soon as possible since the application may cease normal operation.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info:blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Write request sent to slice object.volume in status status terminated abnormally. Write request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease normal operation.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info:oflag=oflag, errno=errno
Open request sent to slice object.volume in status status terminated abnormally. Open request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease to operate normally.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info:blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Read request and writeback request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may not operate normally.
Writeback is a process to read data from other slices in the event of a read error.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
volume has closed down.
Promptly attempt recovery by identifying the cause of failure by referring to GDS log message that was output immediately before the error.
For information on recovery, see "Volume Status Abnormality."
Could not startup class, since valid class configuration database could not be found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.
See "Class Status Abnormality."
Could not startup class, due to insufficient number of valid databases. This message is output when many disks registered with class are unavailable.
See "Class Status Abnormality."
class was closed since no valid class configuration database was found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.
See "Class Status Abnormality."
class was closed due to insufficient number of valid database.
This message is output when many disks registered with class are unavailable.
See "Class Status Abnormality."
Sending request message from node was unsuccessful.
Collect investigation material and contact your local customer support.
Timeout occurred while receiving a reply message from a remote node node.
Collect investigation material and contact your local customer support.
Processing a request message on a remote node node was unsuccessful.
Investigate the node message log and take necessary actions. If recovery is impossible, collect investigation material and contact your local customer support.
Starting volumes within the class class failed on the node node since the status volume volume exists. type is the class type attribute.
volume is in abnormal status. First, you must recover normal status. For information on recovery, see "Volume Status Abnormality."
Starting and putting on standby volumes within the class class failed on the node node since the status volume volume exists. type is the class type attribute.
volume is in abnormal status. First, you must recover normal status. For information on recovery, see "Volume Status Abnormality."
Stopping and putting on standby volumes within the class class failed on the node node since the status volume volume exists. type is the class type attribute.
volume is in abnormal status. First, you must recover normal status. For information on recovery, see "Volume Status Abnormality."
Stopping volumes within the class class failed on the node node since the status volume volume exists. type is the class type attribute.
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "Class Status Abnormality."
Starting volumes failed since the class class has been closed down. type is the class type attribute.
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "Class Status Abnormality."
Starting and putting on standby volumes failed. since the class class has been closed down. type is the class type attribute.
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "Class Status Abnormality."
Stopping and putting on standby volumes failed. since the class class has been closed down. type is the class type attribute.
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "Class Status Abnormality."
Stopping volumes failed since the class class has been closed down. type is the class type attribute.
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "Class Status Abnormality."
Abnormal exclusive control between cluster system nodes occurred.
Since the process cannot be continued, class will be closed.
Collect investigation material and contact your local customer support.
Abnormal exclusive control between cluster system nodes occurred.
Since the process cannot be continued, class could not be started.
Collect investigation material and contact your local customer support.
Transmission failure between cluster system nodes occurred. Since the process cannot be continued, class will be closed.
Collect investigation material and contact your local customer support.
While performing copying between proxy volume proxy and master volume with the OPC function, an I/O error occurred, and the copying process failed. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, and Fujitsu Storage Systems ETERNUS that were output right before the occurrence of the error, and restore.
While performing copying between proxy volume proxy and master volume with the EC function, an I/O error occurred, and the copying process failed. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, and Fujitsu Storage Systems ETERNUS that were output right before the occurrence of the error, and restore.
An error occurred between proxy volume proxy and the master volume when OPC was initiated.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates a class to which the copy source and destination slices belong.
Identify the cause based on log messages of GDS, disk drivers, Fujitsu's ETERNUS storage system and such, and promptly recover the disk.
When stopping OPC between proxy volume proxy and master volume, an error occurred. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, Fujitsu Storage Systems ETERNUS that were output right before the occurrence of the error, and restore.
An error occurred between proxy volume proxy and the master volume when EC was initiated.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates a class to which the copy source and destination slices belong.
Identify the cause based on log messages of GDS, disk drivers, Fujitsu's ETERNUS storage system and such, and promptly recover the disk.
When stopping EC session between proxy volume proxy and master volume, an error occurred. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, and Fujitsu Storage Systems ETERNUS that was output right before the occurrence of the error, and restore.
When temporarily suspending EC session between proxy volume proxy and master volume, an error occurred. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, and Fujitsu Storage Systems ETERNUS that were output right before the occurrence of the error, and restore.
When resuming EC session between proxy volume proxy and master volume, an error occurred. "source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Identify the cause by referring to the log messages for GDS, disk driver, and Fujitsu Storage Systems ETERNUS that were output right before the occurrence of the error, and restore.
A disk registered with GDS was found that it was bound to a RAW device, and the disk was disabled.
disk has been bound to a RAW device.
Cancel the bind to a RAW device using the raw(8) command for the disk registered with GDS. You may not bind disks registered with GDS to RAW devices.
|
Contents
|