From: Andres Salomon <dilinger@mp3revolution.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] mapping blocks to PVs?
Date: Sat Feb 23 15:45:02 2002 [thread overview]
Message-ID: <20020223214540.GA12317@mp3revolution.net> (raw)
I've got a LV that keeps corrupting, made up of several IDE disks. I've
already discovered one of the drives to be flaking out, after various
read tests on the device gave BadCRC/IRQ timeout errors. Read tests on
the other drives succeeded; however, I'm still getting stuff like:
journal_bmap: journal block not found at offset 7180 on lvm(58,0)
and
/dev/site/lvol1: recovering journal
JFS: bad block at offset 7182
How can I figure out which PV is holding block 7180 and 7182?
--
"I think a lot of the basis of the open source movement comes from
procrastinating students..."
-- Andrew Tridgell <http://www.linux-mag.com/2001-07/tridgell_04.html>
next reply other threads:[~2002-02-23 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 15:45 Andres Salomon [this message]
2002-02-24 1:02 ` [linux-lvm] mapping blocks to PVs? Andreas Dilger
2002-02-24 16:58 ` Andres Salomon
2002-02-25 3:50 ` Heinz J . Mauelshagen
2002-02-25 10:00 ` Andreas Dilger
2002-02-26 1:09 ` Andres Salomon
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=20020223214540.GA12317@mp3revolution.net \
--to=dilinger@mp3revolution.net \
--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