[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] Disk problems half way through a pvmove! HELP!

Pvmove was doing its work, happily moving data from one of my old disks (hdh a 160GB Maxtor) but when it got to 46.5% all disk access stopped. I had a look at the console and sure enough there were hundreds of "hdh: lost interrupt" errors. Some googleing has turned up the following explanation:

"Looking at the kernel source revealed only that this message appears when the kernel gets bored waiting for an interrupt from IDE controller (which takes some time, hence the long delays)."

Could anyone tell me if this is correct and any ideas what might cause this? I'm running:
Kernel: 2.6.5-mm1 (for the DM mirror target support)
LVM version: 2.00.08 (2003-11-14)
Library version: 1.00.17-ioctl (2004-04-19)
Driver version: 4.1.0
with a LVM2 VG (vgconverted from LVM1) spread across various Maxtor IDE disks. I tried a pvscan -v to post here but it hung just after "Walking through all physical volumes".

Does anyone have any advice on what to do in this situation? My box is still up but I guess pvmove isn't going to finish on its own (but you can hopefully give me more details on this) so what would happen if I had to kill it? Would I be left with a dead VG or just some data on either disk?

Finally: As pvmove doesn't seem to have any options for moving a specific portion of the data from a drive how can I recover from this if I am left with some data on this potentially bad drive?

Thanks in advance for any info or advice,

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]