From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Hubert Verstraete <hubskml@free.fr>, linux-raid@vger.kernel.org
Subject: Re: RAID5 losing initial synchronization on restart when one disk is spare
Date: Thu, 12 Jun 2008 09:40:47 +1000 [thread overview]
Message-ID: <18512.25215.963409.362155@notabene.brown> (raw)
In-Reply-To: message from Dan Williams on Tuesday June 10
On Tuesday June 10, dan.j.williams@intel.com wrote:
>
> I am able to reproduce this here, and I notice that it does not happen
> with v0.90 superblocks. In the v0.90 case when the array is stopped
> the last disk remains marked as spare. The following hack seems to
> achieve the same effect for v1 arrays, but I wonder if it is
> correct... Neil?
No, not correct.
The fact that a v1 array included spares in the array before recovery
completes is deliberate. It allows recovery to be restarted from
where it got up to if the array is shut down while recovery is
happening.
If you don't mark the drive as a part of the array (though not
in_sync), then there is no opportunity for this optimisation.
Thanks,
NeilBrown
next prev parent reply other threads:[~2008-06-11 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 10:13 RAID5 losing initial synchronization on restart when one disk is spare Hubert Verstraete
2008-06-10 11:57 ` Hubert Verstraete
2008-06-10 22:56 ` Dan Williams
2008-06-11 9:27 ` Hubert Verstraete
2008-06-11 23:40 ` Neil Brown [this message]
2008-06-11 14:44 ` Hubert Verstraete
2008-06-11 23:38 ` Neil Brown
2008-06-12 13:05 ` Hubert Verstraete
2008-06-12 16:59 ` Dan Williams
2008-06-12 18:11 ` Hubert Verstraete
2008-06-11 23:45 ` Neil Brown
2008-06-12 8:03 ` David Greaves
2008-06-12 17:01 ` Dan Williams
2008-06-12 9:12 ` Hubert Verstraete
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=18512.25215.963409.362155@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hubskml@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).