WARNING: read error on status slice object.volume, class=class:
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
Explanation
Read request sent to slice object.volume in status status terminated abnormally. Slice with abnormality will be detached.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: write error on status slice object.volume, class=class:
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
Explanation
Write request sent to slice object.volume in status status terminated abnormally. Slice with abnormality will be detached.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: open error on status slice object.volume, class=class:
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
Explanation
Open request sent to slice object.volume in status status terminated abnormally. Slice with abnormality will be detached.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: read error and writeback error on status slice object.volume, class=class:
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
Explanation
Read request and writeback request sent to slice object.volume in status status terminated abnormally. Slice with abnormality will be detached.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: NVURM write error on disk disk, class=class:
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
Explanation
NVURM write request sent to disk disk terminated abnormally. Although just resynchronization process on volume will be temporarily disabled, it will automatically attempt recovery.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: object.volume: detached status slice by an I/O error, class=class
Explanation
Since an I/O error occurred on slice object.volume in status status, the slice was detached from the volume.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: open error on private slice pslice, oflag=oflag, errno=errno
Explanation
Open request sent to disk private slice pslice terminated abnormally. It will automatically search for a normal alternate disk and attempt recovery.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: read error on private slice p_devno(p_maj,p_min), offset=blknosl, length=length, resid=resid, errno=errno
Explanation
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.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: write error on private slice p_devno(p_maj,p_min), offset=blknosl, length=length, resid=resid, errno=errno
Explanation
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.
If I/O fencing is used, the I/O fencing feature of the GDS may have not been set.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
If I/O fencing is used, make sure that you have configured the I/O fencing feature of the GDS.
For details of the settings, refer to "Installation and Configuration of Related Software" under "Using PRIMECLUSTER in a VMware Environment" described in "PRIMECLUSTER Installation and Administration Guide."
WARNING: close error on private slice p_devno(p_maj,p_min), errno=errno
Explanation
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.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: sdxfunc: pslice: open error, errno=errno
Explanation
The open request for the physical slice pslice terminated abnormally.
The following messages may be output when a node is booted, investigation material is collected (pclsnap or sdxsnap.sh is executed), or the physical disk information update menu in GDS Management View is executed.
a) WARNING: pd_get_info: pslice: open error, errno=6
b) WARNING: pd_set_orig_all: pslice: open error, errno=6
Resolution
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 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.
WARNING: sdxfunc: pslice: read error, errno=errno
Explanation
Read request sent to physical slice pslice terminated abnormally.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: sdxfunc: pslice: write error, errno=errno
Explanation
Write request sent to physical slice pslice terminated abnormally.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: sdxfunc: pslice: ioctl error, request=ioctlcmd, errno=errno
Explanation
The ioctl request sent to physical slice pslice terminated abnormally.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: sdxfunc: pslice: close error, errno=errno
Explanation
Close request sent to physical slice pslice terminated abnormally.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: volume: failed to enable JRM, no available NVURM space, class=class
Explanation
Resuming just resynchronization process on volume volume was unsuccessful.
The following potential causes can be considered:
a) A disk malfunction occurred and there are an insufficient number of normally operating disks which can store the logs (NVURM) for the Just Resynchronization Mechanism (JRM).
b) The size of the private slice of the class class is insufficient and it is impossible to store the logs (NVURM) for the JRM to the private slices.
If one has added to the class a disk with a capacity larger than the disk first registered to the class, it is possible that b) is the cause. For details on insufficient private slice size, refer to "2.3.9 Disk Size."
Resolution
Check the disk status within class. If a disk failure has occurred, identify the cause by referring to disk driver log message, and recover the disk.
If volume is not a mirror volume (such as a single volume), the Just Resynchronization Mechanism is not necessary. This being the case, if volume is not a mirror volume and the cause is b), turning the volume's JRM attribute to off or ignoring this message poses no problems. For turning the JRM attribute off, refer to "B.1.7 sdxattr - Change Objects Attributes."
WARNING: volume: failed to retrieve NVURM from disk disk, class=class
Explanation
NVURM read request of volume from disk was unsuccessful. Just resynchronization will switch to copying of the entire disk.
NVURM is volume update area map information stored in the disk for just resynchronization.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and recover the disk.
WARNING: disk: device: disabled disk, class=class
Explanation
disk is disabled since its data is invalid.
device is the physical disk name corresponding to disk.
Resolution
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.
WARNING: volume: volume synchronization failed, class=class
Explanation
Synchronization copying of volume was unsuccessful.
Resolution
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.
WARNING: volume: volume just resynchronization failed, class=class
Explanation
Just resynchronization of volume was unsuccessful.
Resolution
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.
WARNING: class: unknown class file found
Explanation
Class file class which does not exist in class database file was found while booting the system.
This message is output if starting a node at the time that all disks registered in the class cannot be found due to disk array case down or cable disconnection.
Resolution
Add class which is output at the message to /etc/opt/FJSVsdx/sysdb.d/class.db so that this message will not be output.
Example) If class is class0001
Add class0001 at the position before "# Disk Class List."
# cat class.db class0001 <--- Add # Disk Class List
WARNING: invalid configuration database ID information, sdxerrno=sdxerrno, class=class:
psdevtree
Explanation
Since the configuration database ID information was invalid, private slice psdevtree was not used as the configuration database for class class.
Resolution
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.
WARNING: class: too few valid configuration database replicas
Explanation
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.
Resolution
For details, see "D.1.4 Class Status Abnormality."
WARNING: cannot open message logging file, errno=errno
/var/opt/FJSVsdx/msglog/daemon.log
Explanation
Opening GDS log file was unsuccessful.
This message is output via rsyslogd. Although the message will not be output on GDS logfile, it does not affect other processes.
Resolution
Collect investigation material, and contact field engineers regarding recovery.
WARNING: cannot write message logging file, errno=errno
/var/opt/FJSVsdx/msglog/sdxservd.log
Explanation
Writing to GDS log file was unsuccessful.
This message is output via rsyslogd. Although the message will not be output on GDS logfile, it does not affect other processes.
Resolution
Collect investigation material and contact field engineers.
WARNING: failed to reply message to node node, details
Explanation
Replying to remote node node was unsuccessful.
Resolution
Collect investigation material and contact field engineers.
WARNING: class: failed to change class resource status on remote node node, status=new-status, sdxerrno=sdxerrno
Explanation
Changing class resource status to new-status on a remote node node was unsuccessful.
Resolution
Collect investigation material and contact field engineers.
WARNING: sdxfunc: no enough address space, osfunc=osfunc, errno=errno
Explanation
The OS osfunc function returned an error. The error number is errno.
Resolution
Confirm you have sufficient memory or swap area.
WARING: respawned daemon daemon successfully
Explanation
Although daemon terminated abnormally, it completed normally by restarting. This message is output via rsyslogd.
Resolution
After daemon ended abnormally, the recovery function restarted the daemon normally. Therefore, the abnormal end has no influence on the operation and restoration work is not necessary.
If you want to identify the cause of the daemon abnormal end, collect investigation material and contact field engineers.
WARNING: device: failed to restore VTOC on disk, sdxerrno=sdxerrno
Explanation
Recovering physical disk device format information was unsuccessful. Disk failure may have occurred.
Resolution
Use parted(8) command to recover format information.
WARNING: volume: cannot copy to one or more slices in volume
Explanation
Copying process could not be performed on some slices within volume.
Resolution
Execute synchronization copying as needed.
WARNING: device: write error, errno=errno
Explanation
A write error occurred in physical disk device and recovering the disk label of device failed. A disk failure may have occurred.
Resolution
To recover the disk label of device, use the parted(8) command. If device is write-locked by the disk unit's copy function, no action is required.
WARNING: device: read error, errno=errno
Explanation
A read error occurred in physical disk device and recovering the disk label of device failed. A disk failure may have occurred.
Resolution
To recover the disk label of device, use the parted(8) command.
WARNING: proxy: too many EC/OPC sessions
Explanation
The number of EC or OPC sessions within the physical disk (LU) or the disk array body has reached the upper limit of supported concurrent sessions. For this reason, a new EC or OPC session cannot be started. Copying is started using the soft copy function.
Resolution
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.
WARNING: proxy: failed to start OPC, source=disk.volume, target=disk.volume, class=class
Explanation
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.
Resolution
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 ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
WARNING: proxy: failed to start EC session, source=disk.volume, target=disk.volume, class=class
Explanation
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.
Resolution
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 ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
WARNING: backup_efi_files_grub: details
Explanation
In the process of setting or canceling the system disk mirroring, the grub.conf file or the grub.cfg file cannot be backed up.
details indicates the cause of the error.
Resolution
If no other message was output, the error has no effect on the system. There is no need to work around.
If some other message was output, work around the error message.
WARNING: backup_efi_files_initrd: details
Explanation
In the process of setting or canceling the system disk mirroring, an initial RAM disk cannot be backed up.
details indicates the cause of the error.
Resolution
If no other message was output, the error has no effect on the system. There is no need to work around.
If some other message was output, work around the error message.
WARNING: failed to update netmirror DB file, class=class, volume=volume
Explanation
The device information of the netmirror group has failed to be updated.
Resolution
If the INVALID status slice exists within the netmirror volume volume, and other nodes are LEFTCLUSTER or DOWN.
Synchronization copying of netmirror volume fails.
Restore the node first. After that, execute the sdxcopy -B command, for example, to perform the synchronization copying.
For how to recover from the LEFTCLUSTER state, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
Otherwise
Take the following procedure to restore.
Restore the file system or file with all of the nodes.
When no available capacity under /var/opt
Delete unnecessary files to secure 100MB or more free capacities under /var/opt. After that, restart the system.
When enough capacity available under /var/opt
Output the /var/opt/FJSVsdx/log/.sdxnetmirror_disable.db file by the cat command, and check that the output is not garbled.
If it is garbled, delete the file and then restart the system.
If /var/opt on all of the nodes has capacity and the file is not garbled, collect investigation material and contact field engineers.
Depending on the slice status within the netmirror volume volume, take the following procedure.
When the NOUSE status slice does not exists in the netmirror volume volume.
Synchronization copying of netmirror volume fails.
Perform the synchronization copying by using the sdxcopy -B command, for example.
When the NOUSE status slice exists in the netmirror volume volume.
Restore NOUSE status of the slice. For details, see "(6) Slice configuring the volume is in NOUSE status." in "D.1.1 Slice Status Abnormality."
