On Mon, Sep 10, 2001 at 01:27:09PM +0200, Heinz J . Mauelshagen wrote:
> But I wonder, why in your case the locking of the PE failed. Are you able to
> reporduce your case and provide the error code?
It was reproducable at the time - now the disk in question has been
replaced. If it's interesting enough, I can make a phone call and see if
I can get the broken disk back.
The error_occured in the pe_lock() call at the beginning of the
move-operation - the one that I commented out in patch.
This is the kernel-log from the time (well, I think it was from the time
I ran pe_move):
Sep 6 18:10:01 argus kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 6 18:10:01 argus kernel: hdd: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=155058176, sector=0
Sep 6 18:10:01 argus kernel: lvm -- lvm_blk_ioctl: unknown command 587
Sep 6 18:10:01 argus kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Sep 6 18:10:01 argus kernel: hdd: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=155058176, sector=0
Sep 6 18:10:01 argus kernel: lvm -- lvm_blk_ioctl: unknown command 587
and:
Sep 6 18:15:51 argus kernel: lvm -- lvm_blk_ioctl: unknown command 587
Sep 6 18:15:55 argus last message repeated 213 times
Sep 6 18:15:55 argus kernel: hdd: read_intr: status=0x59 { DriveReady SeekComplete DataRequest E rror }
Sep 6 18:15:55 argus kernel: hdd: read_intr: error=0x40 { UncorrectableError }, LBAsect=11801433 2, sector=118014332
Sep 6 18:15:55 argus kernel: end_request: I/O error, dev 16:40 (hdd), sector 118014332
The kernel is standard 2.4.8 without the LVM-patches. The usersspace
tools are version 1.0.1-rc2.
--
Ragnar Kjørstad
Big Storage
