Top
PRIMECLUSTER Global Disk Services  Configuration and AdministrationGuide 4.7

C.4.2 Warning Messages (62000-62099)


62000

WARNING: spare disk disk too small

Explanation

The size of disk is too small and may not function as a spare disk.

Resolution

Specify a larger disk, and execute the command again.


62001

WARNING: device: write error, errno=errno

Explanation

A write error occurred in physical disk device.

Resolution

If device is a write-locked disk that is connected to a switch group, no action is required. Otherwise, remove device from the class and check the status of device.


62002

WARNING: group: free blocks are reduced

Explanation

Free blocks on group were reduced.

Resolution

You may not be able to create a volume with sufficient capacity. Execute commands as needed and attempt recovery.


62003

WARNING: another disk must be connected to group

Explanation

You must connect another disk to group.

Resolution

Connect another disk.


62004

WARNING: object: copying not completed successfully

Explanation

Synchronization copying did not complete successfully.

Resolution

Disk failure may have occurred. Identify the cause by referring to GDS log message and rsyslogd message.


62005

WARNING: object: gave up wait for the completion of copying by a cancel request

Explanation

Synchronization copying was canceled before completion.

Resolution

Check the status of the object object. If the copying is in progress, there is no need to work around. If it is not in progress, re-execute the copying where it is necessary.
For details, see "Appendix B Command Reference."


62007

WARNING: group: no spare disk available

Explanation

There is no valid spare disk in group.

Resolution

Define a spare disk as needed.


62008

WARNING: object.volume: cannot attached due to in status status

Explanation

Slice object.volume could not be attached since it is in status status.

Resolution

Check the slice status and cancel status status as needed.


62009

WARNING: volume: no need to resize volume

Explanation

There was no need to resize the volume volume.

Resolution

No particular resolution required.


62010

WARNING: disk.volume: special file(s) not found

Explanation

Special file for slice disk.volume could not be found.

Resolution

No particular resolution required.


62011

WARNING: node: node in stopped status 

Explanation

node is in STOP status.

Resolution

No particular resolution required. However, promptly activating the node is recommended.


62012

WARNING: node: node in abnormal status

Explanation

node is in abnormal status.

Resolution

No particular resolution required. However, promptly recovering the node and activating it normally is recommended.


62013

WARNING: object: already in status status

Explanation

object is already in status status.

Resolution

No particular resolution required.


62014

WARNING: disk : device : write error, errno=errno

Explanation

A write error occurred on physical disk device.

Resolution

If device is a write-locked disk that is connected to a switch group, no action is required. In other situations, have device exchangeable and check its status.


62015

WARNING: disk : device : node: write error, errno=errno

Explanation

A write error occurred on physical disk device on node node.

Resolution

If device is a write-locked disk that is connected to a switch group, no action is required. In other situations, have device exchangeable and check its status.


62016

RNING: object: no need to update attribute value

Explanation

There was no need to change object attributes.

Resolution

No particular resolution required.


62017

WARNING: pslice: entry in /etc/fstab not updated, unsupported file system type fstype

Explanation

Entry in the /etc/fstab file relevant to the physical slice pslice was not updated since fstype is a file system type not supported by the sdxroot command.

Resolution

Edit the /etc/fstab file or change the file system configuration according to need.


62018

WARNING: correct /etc/fstab and file system configuration before rebooting, or system may not be booted

Explanation

The /etc/fstab file contains an invalid entry. When an entry for a file system, such as / (root), /usr, and /var, essential to system start-up is invalid, it will be impossible to start the system if rebooted.

Resolution

Refer to a GDS's WARNING message output just before this message and pinpoint the invalid entry in the /etc/fstab file. Be sure to repair the /etc/fstab file and the file system configuration as needed prior to rebooting the system.


62019

WARNING: volume: entry in /etc/fstab not updated, unsupported file system type fstype

Explanation

Since file system type fstype is not supported, entry in /etc/fstab file for volume could not be updated.

Resolution

Directly edit /etc/fstab as necessary.


62020

WARNING: ignored parameter param for EC

Explanation

Since EC function will be used for copying, parameter param was ignored.


62021

WARNING: ignored parameter param for OPC

Explanation

Since OPC function will be used for copying, parameter param was ignored.


62022

WARNING: ignored parameter param for TimeFinder

Explanation

Parameter param was ignored for copying with TimeFinder.


62023

WARNING: ignored parameter param for SRDF

Explanation

Parameter param was ignored for copying with SRDF.


62024

WARNING: proxy: no session

Explanation

No copy session exists between the proxy proxy and the master

Resolution

No special action is required.


62025

WARNING: physical disk not found

Explanation

After the system is restarted, some physical disks cannot be recognized from OS.

When the physical disk cannot be recognized, the asterisk (*) is displayed in DEVNAM field of the sdxinfo -D command output result.

Resolution

The unrecognized physical disk may have a failure. Check if the disk has a failure. Restore the failed disk by replacing it with the new disk, for example, and then execute the command again.


62026

WARNING: device: failed to delete partition table

Explanation

The partition table failed to be deleted.

Resolution

The physical disk device may have a failure.

Check if the disk has a failure or not.

If device has a failure, restore the disk by replacing it with another disk, for example.

If device is normal, delete device from the class before restarting the system. After that, delete all the partitions of device by using a command such as the parted(8) command.