All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <lvm@ragnark.vestdata.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] pv_move_pe() error again :/
Date: Tue, 11 Sep 2001 19:26:43 +0200	[thread overview]
Message-ID: <20010911192643.A31067@vestdata.no> (raw)
In-Reply-To: <20010911163120.F20767@sistina.com>; from mauelshagen@sistina.com on Tue, Sep 11, 2001 at 04:31:20PM +0200

On Tue, Sep 11, 2001 at 04:31:20PM +0200, Heinz J . Mauelshagen wrote:
> > 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
> 
> Ragnar, the block ioctl error the lvm driver shows is not related to the locking
> of a physical extent, because that is achived by the PE_LOCK_UNLOCK ioctl
> (0x50 BTW) using the character ioctl function.
> Wasn't able to find that ioctl grepping the kernel sources.
> Could it be some application checking devices regularly like a desktop
> CD-ROM tool or something?

Could it be badblocks?


> I gues your problem was just the dying disk and therefore temporarily avoiding
> the read() check in pv_move_pe() should have catched this one as well.

I ran pv_move with debugging enabled, and it showed that it died in
lock_pe(). I'll try to reproduce this next time I find I broken disk.



-- 
Ragnar Kjørstad
Big Storage

  reply	other threads:[~2001-09-11 17:26 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
2001-09-10 16:13                   ` FEJF
2001-09-11 14:31                   ` Heinz J . Mauelshagen
2001-09-11 17:26                     ` Ragnar Kjørstad [this message]
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=20010911192643.A31067@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.