LV Status available/syncd but PV unavailable

[Torsten.]

Please read my first comment again ... and answer the question about your OS.

Consider to attach a "swlist" output.

[YA Unix Admin]

the dd is still running
time now is
Tue Jul 15 13:14:54 EDT 2008
time to kill it I suppose...??.. give up on it

about the patch level ... I inherited these old(ish) servers and we never touch them unless they break. So this server has been running un- harassed for long time .. and I'm sure the patches are out of date .. but the only thing that could have "happened" is the hardware died - no soft changes were made. I expected an obvious disk error /hardware error .. *somewhere* - but no, was not what I got.

[Torsten.]

Based on the ioscan I assume this is an L-class server, probably running an early 11.11 or even 11.00.

Years ago there were problems like your with failed disks and LVM - fixed by several LVM patches.

If your system is not patched, I guess you have a failed disk and LVM is not able to detect this correctly.

You should wait for dd to finish or stop, search the root mailbox and syslog for related errors.

[YA Unix Admin]

I see what you mean about patches ... I found these bits and pieces

from syslog

Jul 15 08:29:08 nickel vmunix: vxfs: mesg 055: vx_metaioerr - /dev/vg02/lvol1 file system meta data write error
Jul 15 08:29:23 nickel vmunix: vxfs: mesg 031: vx_disable - /dev/vg02/lvol1 file system disabled

from dmesg

vxfs: mesg 056: vx_dataioerr - /dev/vg02/lvol02 file system file data read error
vxfs: mesg 055: vx_metaioerr - /dev/vg02/lvol02 file system meta data write error
vxfs: mesg 020: vx_logerr - /dev/vg02/lvol02 file system log error 5
vxfs: mesg 031: vx_disable - /dev/vg02/lvol02 file system disabled
vxfs: mesg 055: vx_metaioerr - /dev/vg02/lvol1 file system meta data write error
vxfs: mesg 031: vx_disable - /dev/vg02/lvol1 file system disabled
~

so the prob reason i did not get an obvious error .. is because we are so far out of patches. I'll buy that ...

This is an old box and I will make management aware of the unpatched situation. I ain't inclined to open that pandora's box at this point ...


In the mean time the dd is still sitting there ... fwiw sar does not show the disk doing anything. Is there anyway to see if it's doing anything ..

(Thanks for all you help btw )

[Torsten. · Accepted solution]

The dd may hang because of the bad disk. Disks can die in several ways - fast or just slow ... but I'm sure this disk is bad and needs to be replaced because of all the I/O errors.

[YA Unix Admin]

Now that found something in the logs ... I'll settle for that as my error.


Thanks for all the fish :)

[YA Unix Admin]

Because of the not current patches .. the os prob can't give pretty errors ... but dmesg does show the disk having problems.