From: NeilBrown <neilb@suse.de>
To: Jon Forrest <jlforrest@berkeley.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery Optimization?
Date: Sat, 19 Feb 2011 15:54:50 +1100 [thread overview]
Message-ID: <20110219155450.4c940485@notabene.brown> (raw)
In-Reply-To: <ijn1hs$8nl$1@dough.gmane.org>
On Fri, 18 Feb 2011 16:06:43 -0800 Jon Forrest <jlforrest@berkeley.edu> wrote:
> I'm just learning how the md system works so what
> I'm going to say might not be sensible.
>
> I read that if a disk in a RAID5 set goes bad, and the
> disk is replaced by a new one, that the recovery operation
> takes place blindly. By this I mean that all the stripes
> will be read so that new parity blocks can be written.
> But, there might be stripes that contain only blocks
> that aren't used by the filesystem. Wouldn't it be
> good when doing recovery if some kind of allocation
> map were created so that unused stripes wouldn't be
> restored. I would think that depending on how full
> the disk is that this could save time.
>
> Is this reasonable?
>
> Cordially,
http://neil.brown.name/blog/20110216044002#5
NeilBrown
prev parent reply other threads:[~2011-02-19 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 0:06 Recovery Optimization? Jon Forrest
2011-02-19 0:37 ` Mathias Burén
2011-02-19 4:54 ` NeilBrown [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=20110219155450.4c940485@notabene.brown \
--to=neilb@suse.de \
--cc=jlforrest@berkeley.edu \
--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).