From: Lars Marowsky-Bree <lmb@suse.de>
To: bmoon <bo@anthologysolutions.com>, Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Really need RESYNC at the time of RAID1&5 creation?
Date: Tue, 1 Jul 2003 00:03:08 +0200 [thread overview]
Message-ID: <20030630220308.GQ12240@marowsky-bree.de> (raw)
In-Reply-To: <00b901c33f4f$715be540$6401a8c0@bmoon>
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
next prev parent reply other threads:[~2003-06-30 22:03 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 [this message]
2003-06-30 22:11 ` Corey McGuire
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=20030630220308.GQ12240@marowsky-bree.de \
--to=lmb@suse.de \
--cc=bo@anthologysolutions.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.