From: Andre Noll <maan@systemlinux.org>
To: Dave Moon <p.b.w.tortilla@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
Date: Wed, 25 Jun 2008 18:13:57 +0200 [thread overview]
Message-ID: <20080625161357.GH23944@skl-net.de> (raw)
In-Reply-To: <41931C59-9A91-47A6-A81C-EC14001DA95B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On 15:37, Dave Moon wrote:
> 1. If mdadm encounters a bit error during a RAID 6 rebuild, will it
> just give up on that particular file and move on to recover other data
> on the array? Or will it trash the entire array?
The kernel will stop the array and give up.
> 2. Is it possible to cheat mdadm by somehow replacing the new "raid
> metadata" on the 6 drives with the old data on the 2 drives? Will it
> make mdadm think the array is clean, consistent and nothing ever
> happened?
> Please do note that I did not write ANY new data onto the RAID 6 array
> from the time it was degraded until the time I brought it down with (--
> stop).
Use --force, Luke. Man mdadm(8):
-f, --force Assemble the array even if some superblocks
appear out-of-date
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-06-25 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 6:37 How to avoid complete rebuild of RAID 6 array (6/8 active devices) Dave Moon
2008-06-25 16:13 ` Andre Noll [this message]
2008-06-27 10:40 ` Neil Brown
2008-06-29 21:58 ` Bill Davidsen
2008-07-14 10:44 ` Matthias Urlichs
2008-07-14 16:14 ` David Greaves
2008-07-14 16:54 ` David Lethe
2008-07-14 22:58 ` Matthias Urlichs
2008-07-14 23:54 ` Richard Scobie
2008-07-15 0:05 ` Matthias Urlichs
2008-07-15 14:24 ` Keld Jørn Simonsen
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=20080625161357.GH23944@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=p.b.w.tortilla@gmail.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).