From: Fredrik Tolf <fredrik@dolda2000.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove on broken disk
Date: Fri, 26 Aug 2005 18:47:59 +0200 [thread overview]
Message-ID: <1125074879.2225.46.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <3361914A535DD23CBBC6B90F@dhcp-2-206.wgops.com>
On Fri, 2005-08-26 at 10:13 -0600, Michael Loftis wrote:
> --On August 26, 2005 3:26:26 PM +0200 Fredrik Tolf <fredrik@dolda2000.com>
> wrote:
> > I've got a related question as well, but it's not really LVM-related.
> > The thing is that there's something strange with either the IDE chipset
> > (a Promise card) or the corresponding driver that this disk is connected
> > to, which causes a kernel panic every time a read from a bad sector is
> > attempted. I figure I can "fix" that by connecting the drives to a
> > different computer while pvmoving, but I wouldn't prefer to do that, as
> > it causes downtime. Does someone on the list know of this problem and
> > how to work around it? I figure that I can attempt to fix the driver
> > bug, but I wouldn't prefer to experiment with that system...
>
> Actually, if you're having PV errors, it might be the filesystem driver
> that's panic-ing....you'll need to run the output through ksymoops and find
> out where it's dieieng. If you've corrupted filesystem data, that's the
> much more likely target (although what you're hypothesizing isn't
> impossible, I've just never seen that).
Thanks for the tip, but the panic message gave enough info for me to
conclude that it's a NULL pointer dereference in ide_timer_expiry.
Unfortunately, I hadn't compiled the kernel with debugging support,
however, so it's hard for me to determine just where in ide_timer_expiry
at this point.
Fredrik Tolf
prev parent reply other threads:[~2005-08-26 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 13:26 [linux-lvm] pvmove on broken disk Fredrik Tolf
2005-08-26 16:13 ` Michael Loftis
2005-08-26 16:47 ` Fredrik Tolf [this message]
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=1125074879.2225.46.camel@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).