| PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
|
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. Slice with abnormality will be detached.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and 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. Slice with abnormality will be detached.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and 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. Slice with abnormality will be detached.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and 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. Slice with abnormality will be detached.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
volume info:devno(maj,min)=v_devno(v_maj,v_min)
volume=volume, class=class
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
NVURM write request sent to disk disk terminated abnormally.
Although just resynchronization process on volume will be temporarily disabled, it will automatically attempt recovery.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Since an I/O error occurred on slice object.volume in status status, the slice was detached from the volume.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Open request sent to disk private slice pslice terminated abnormally.
It will automatically search for a normal alternate disk and attempt recovery.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Read request sent to disk private slice p_devno(p_maj,p_min) terminated abnormally. It will automatically search for a normal alternate disk and attempt recovery.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Write request sent to disk private slice p_devno(p_maj,p_min) terminated abnormally. It will automatically search for a normal alternate disk and attempt recovery.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Close request sent to disk private slice p_devno(p_maj,p_min) terminated abnormally. It will automatically search for a normal alternate disk and attempt recovery.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
The open request sent to the physical slice pslice terminated abnormally.
The following messages may be output when a node is booted, investigation material is collected (fjsnap or sdxsnap.sh is executed), or the physical disk information update menu in GDS Management View is executed.
WARNING: pd_get_info: pslice: open error, errno=6
WARNING: pd_set_orig_all: pslice: open error, errno=6
A disk failure may have occurred. Identify the cause by referring to disk driver log messages, and recover the disk.
However, in the following situations, GDS is behaving normally and the messages a) and b) may be ignored.
In the messages a) and b), pslice is a physical slice of a disk unit previously removed. In this situation, delete the device special file for pslice, and these messages will no longer be output.
In the messages a) and b), pslice is a physical disk slice of a physical disk not registered with GDS.
Read request sent to physical slice pslice terminated abnormally.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Write request sent to physical slice pslice terminated abnormally.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
The ioctl request sent to physical slice pslice terminated abnormally.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Close request sent to physical slice pslice terminated abnormally.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
Resuming just resynchronization process on volume was unsuccessful due to insufficient number of normal disks.
Check the disk status within class. Disk failure may have occurred.
Identify the cause by referring to disk driver log message, and recover the disk.
NVURM read request of volume from disk was unsuccessful. Just resynchronization will switch to copying of the entire disk.
NVURM is a volume update area map information stored in the disk for just resynchronization.
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
disk is disabled since its data is invalid. device is the physical disk name corresponding to disk.
Disk configuration may have been wrongly changed or disk data could be damaged. Check for improper connection change of I/O cables and disk swap.
Also check for disk driver log message regarding the disk in question, and attempt recovery.
Synchronization copying of volume was unsuccessful.
Attempt recovery by identifying the cause of failure by referring to GDS log message and disk driver message that were output immediately before the error.
Just resynchronization copying of volume was unsuccessful.
Attempt recovery by identifying the cause of failure by referring to GDS log message and disk driver message that were output immediately before the error.
Class file class which does not exist in class database file was found while booting the system.
psdevtree
Since the configuration database ID information was invalid, private slice psdevtree was not used as the configuration database for class class.
Disk configuration may have been wrongly changed or disk data could be damaged. Check for improper connection change of I/O cables and disk swap. Also check for disk driver log message regarding the disk in question, and attempt recovery.
There are not sufficient valid configuration databases 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."
/var/opt/FJSVsdx/msglog/daemon.log
Opening GDS log file was unsuccessful. This message will be output via syslog. Although the message will not be output on GDS logfile, it does not affect other processes.
Collect investigation material, and contact your local customer support regarding recovery.
/var/opt/FJSVsdx/msglog/sdxservd.log
Writing to GDS log file was unsuccessful. This message will be output via syslog. Although the message will not be output on GDS logfile, it does not affect other processes.
Collect investigation material and contact your local customer support.
Replying to remote node node was unsuccessful.
Collect investigation material and contact your local customer support.
Changing class resource status to new-status on a remote node node was unsuccessful.
Collect investigation material and contact your local customer support.
The OS osfunc function returned an error. The error number is errno.
Confirm you have sufficient memory or swap area.
Although daemon terminated abnormally, it completed normally by restarting. This message will be output via syslog.
To identify the cause of daemon terminating abnormally, collect investigation material and contact your local customer support.
Recovering physical disk device format information was unsuccessful. Disk failure may have occurred.
Use format(1M) command to recover format information.
Since a command is already registered with NVRAMRC, use-nvramrc? parameter could not be set to "true."
For details of advisory notices, see "System Disk Mirroring."
Copying process could not be performed on some slices within volume.
Execute synchronization copying as needed.
A write error occurred in physical disk device and recovering the VTOC of device failed. A disk failure may have occurred.
To recover the VTOC of device, use the format(1M) command. If device is write-locked by the disk unit's copy function, no action is required.
A read error occurred in physical disk device and recovering the VTOC of device failed. A disk failure may have occurred.
To recover the VTOC of device, use the format(1M) command.
special
An error may have occurred on the mirrored boot device special.
Disk failure may have occurred. Identify the cause by referring to the disk driver log message and such, and recover the disk.
The diag-switch? parameter stored in NVRAM (non-volatile memory) on the main unit is true, and the system was booted from the diagnostic boot device.
Change the diag-switch? variable to false where necessary and reboot the system.
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. Copying is started using the soft copy function.
To make copying by EC or OPC available, cancel the relationship between the proxy volume proxy and the master volume, 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.
An error occurred when OPC was started between the proxy volume proxy and the master volume. "source" is the copy source slice name, "target" is the copy destination slice name, and "class" is the name of the class to which the copy source slice and the copy destination slice belong. Copying is started between proxy and the master using the soft copy function.
The cause of this error may derive from a faulty disk array unit. 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 when an EC session was started between the proxy volume proxy and the master volume. "source" is the copy source slice name, "target" is the copy destination slice name, and "class" is the name of the class to which the copy source slice and the copy destination slice belong. Copying is started between proxy and the master using the soft copy function.
The cause of this error may derive from a faulty disk array unit. 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.
|
Contents
|