From: Andres Salomon <dilinger@mp3revolution.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] mapping blocks to PVs?
Date: Sun Feb 24 16:58:02 2002 [thread overview]
Message-ID: <20020224225832.GA4123@mp3revolution.net> (raw)
In-Reply-To: <20020224000143.D12832@lynx.adilger.int>
Ok, assuming the block/sector stuff is correct:
--- Physical extents ---
PE LV LE Disk sector
00000 /dev/site/lvol1 00000 33144
00001 /dev/site/lvol1 00001 65912
badblocks(2) is not picking up those blocks as being bad; this means I
need to manually remove the first LE from this LV. I assume I can
do something similar to `pvmove -n /dev/site/lvol1:0 /dev/hdf1 /dev/hdb1`
(hdf1 is the one causing problems, but I can't simply remove the PV from the
VG w/out deleting lots of stuff). However, how do I lvreduce from the
beginning of the LV? Is that possible?
On Sun, Feb 24, 2002 at 12:01:43AM -0700, Andreas Dilger wrote:
>
> On Feb 23, 2002 16:45 -0500, Andres Salomon wrote:
> > 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 "lvdisplay -v" or "pvdisplay -v" or similar will show the _sector_
> numbers for each PE. Note that for ext3, the block numbers reported are
> 4kB blocks (usually, check with dumpe2fs -h), so you are probably looking
> for sectors 7180*8 and 7182*8.
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
"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 prev parent reply other threads:[~2002-02-24 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 15:45 [linux-lvm] mapping blocks to PVs? Andres Salomon
2002-02-24 1:02 ` Andreas Dilger
2002-02-24 16:58 ` Andres Salomon [this message]
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=20020224225832.GA4123@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