From: Matthias Julius <jnews@julius-net.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid5 with 2 bad drives
Date: Wed, 23 Feb 2005 08:35:13 -0500 [thread overview]
Message-ID: <877jkzbdri.fsf@julius-net.net> (raw)
In-Reply-To: 421C216B.8050209@h3c.com
Mike Hardy <mhardy@h3c.com> writes:
> I posted a raid5 parity calculator implemented in perl a while back (a
> couple weeks?) that is capable of taking your disk geometry, the RAID
> LBA you're interested in, and finding the disk sector it belongs to.
>
> I honestly don't remember if it can go the other way, but I'm not sure
> why it couldn't? Its possible that bad blocks may simply be in the
> parity chunk of the stripe too. Once you've got the RAID LBA you can
> use the methods in the BadBlockHowto to find the file
That helps. Although there is a typo in line 139. See diff below.
When I know the RAID LBA how do I find out to which LV it belongs and
which sector it is in there? But, I guess I better ask that on a LVM
list.
Matthias
--- raid5calc.orig 2005-02-23 08:26:43.721332354 -0500
+++ raid5calc 2005-02-23 08:30:12.673100526 -0500
@@ -136,7 +136,7 @@
# Testing only -
# Check to see if the result I got is the same as what is in the block
open (DEVICE, "<" . $component{"device"})
- || die "Unable to open device " . $compoent{"device"} . ": " . $! . "\n";
+ || die "Unable to open device " . $component{"device"} . ": " . $! . "\n";
seek(DEVICE, $device_offset, 0)
|| die "Unable to seek to " . $device_offset . " device " . $xor_devices{$i} . ": " . $! . "\n";
read(DEVICE, $data, ($sectors_per_chunk * 512))
prev parent reply other threads:[~2005-02-23 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:43 Raid5 with 2 bad drives Matthias Julius
2005-02-22 17:03 ` Gordon Henderson
2005-02-23 0:40 ` Matthias Julius
2005-02-23 6:23 ` Mike Hardy
2005-02-23 13:35 ` Matthias Julius [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=877jkzbdri.fsf@julius-net.net \
--to=jnews@julius-net.net \
--cc=linux-raid@vger.kernel.org \
/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.