From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pv_move_pe() error again :/
Date: Mon, 10 Sep 2001 17:38:51 +0200 [thread overview]
Message-ID: <20010910173851.A3751@vestdata.no> (raw)
In-Reply-To: <20010910132709.G31313@sistina.com>; from mauelshagen@sistina.com on Mon, Sep 10, 2001 at 01:27:09PM +0200
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
next prev parent reply other threads:[~2001-09-10 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 15:28 [linux-lvm] pv_move_pe() error again :/ FEJF
2001-09-06 20:05 ` Ragnar Kjørstad
2001-09-06 23:41 ` FEJF
2001-09-07 9:43 ` Ragnar Kjørstad
2001-09-07 11:36 ` FEJF
2001-09-09 22:16 ` Ragnar Kjørstad
2001-09-09 23:51 ` FEJF
2001-09-10 8:39 ` Ragnar Kjørstad
2001-09-10 11:27 ` Heinz J . Mauelshagen
2001-09-10 11:45 ` FEJF
2001-09-10 13:43 ` Heinz J . Mauelshagen
2001-09-10 13:49 ` FEJF
2001-09-10 15:38 ` Ragnar Kjørstad [this message]
2001-09-10 16:13 ` FEJF
2001-09-11 14:31 ` Heinz J . Mauelshagen
2001-09-11 17:26 ` Ragnar Kjørstad
2001-09-10 11:53 ` FEJF
2001-09-07 10:46 ` Heinz J . Mauelshagen
2001-09-07 11:45 ` FEJF
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010910173851.A3751@vestdata.no \
--to=lvm@ragnark.vestdata.no \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox