From: "Corey McGuire" <coreyfro@coreyfro.com>
To: linux-raid@vger.kernel.org
Subject: Re: Really need RESYNC at the time of RAID1&5 creation?
Date: Mon, 30 Jun 2003 15:11:57 -0700 [thread overview]
Message-ID: <200306301511570187.67A9C782@shargaas.coreyfro.com> (raw)
In-Reply-To: <20030630220308.GQ12240@marowsky-bree.de>
Just my 2 cents but were it not for the initial resync last week, I may
have never known that my RAID was shafted.
sure, once it synced, it took two hours, but that is a price I am willing
to pay...
*********** REPLY SEPARATOR ***********
On 7/1/2003 at 12:03 AM Lars Marowsky-Bree wrote:
>On 2003-06-30T14:34:51,
> bmoon <bo@anthologysolutions.com> said:
>
>> Hi Neil & Raiders,
>>
>> I am not quite sure if we really need to resync the array at the time of
>> RAID 1 or RAID 5 array creation. I tried and tested without RESYNC by
>> modifying "case1" and "case2" from MDADM source below, I could not
notice
>> any problems or issues.
>
>It's necessary to ensure consistency of the RAID, so that later, you can
>detect whether the RAID has scrambled some of your disk.
>
>Otherwise, you'd never know whether it wouldn't still be an artifact
>leftover from the creation of the array.
>
>Another option would be a bitmap of used chunks so you could tell one
>from the other, but that wouldn't make as much sense on a heavily used
>array. So just initialize it once.
>
>
>Sincerely,
> Lars Marowsky-Brée <lmb@suse.de>
>
>--
>SuSE Labs - Research & Development, SuSE Linux AG
>
>"If anything can go wrong, it will." "Chance favors the prepared (mind)."
> -- Capt. Edward A. Murphy -- Louis Pasteur
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
/\/\/\/\/\/\ Nothing is foolproof to a talented fool. /\/\/\/\/\/\
coreyfro@coreyfro.com
http://www.coreyfro.com/
http://stats.distributed.net/rc5-64/psummary.php3?id=196879
ICQ : 3168059
-----BEGIN GEEK CODE BLOCK-----
GCS d--(+) s: a-- C++++$ UBL++>++++ P+ L+ E W+++$ N+ o? K? w++++$>+++++$
O---- !M--- V- PS+++ PE++(--) Y+ PGP- t--- 5(+) !X- R(+) !tv b-(+)
Dl++(++++) D++ G+ e>+++ h++(---) r++>+$ y++*>$ H++++ n---(----) p? !au w+
v- 3+>++ j- G'''' B--- u+++*** f* Quake++++>+++++$
------END GEEK CODE BLOCK------
Home of Geek Code - http://www.geekcode.com/
The Geek Code Decoder Page - http://www.ebb.org/ungeek//
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2003-06-30 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 21:34 Really need RESYNC at the time of RAID1&5 creation? bmoon
2003-06-30 22:03 ` Lars Marowsky-Bree
2003-06-30 22:11 ` Corey McGuire [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=200306301511570187.67A9C782@shargaas.coreyfro.com \
--to=coreyfro@coreyfro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox