From: Neil Brown <neilb@suse.de>
To: Peter Rabbitson <rabbit@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: question about --assume-clean
Date: Sun, 10 Jun 2007 08:31:34 +1000 [thread overview]
Message-ID: <18027.10822.429848.873647@notabene.brown> (raw)
In-Reply-To: message from Peter Rabbitson on Saturday June 9
On Saturday June 9, rabbit@rabbit.us wrote:
> Hi,
>
> I am about to create a large raid10 array, and I know for a fact that
> all the components are identical (dd if=/dev/zero of=/dev/sdXY). Is it
> safe to pass --assume-clean and spare 6 hours of reconstruction, or are
> there some hidden dangers in doing so?
No, there are no hidden dangers.
--assume-clean is generally quite safe with mirroring levels (raid1,
raid10). The only issue is that if you do a regular 'check', then it
will reports lots of issues. If do a 'repair' it will fix the issues.
With raid4/5/6, --assume-clean is *not* safe if there is any doubt that
the drive are not already in an in-sync state.
NeilBrown
prev parent reply other threads:[~2007-06-09 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 17:40 question about --assume-clean Peter Rabbitson
2007-06-09 22:31 ` Neil Brown [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=18027.10822.429848.873647@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rabbit@rabbit.us \
/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).