From: Jon Forrest <jlforrest@berkeley.edu>
To: linux-raid@vger.kernel.org
Subject: Recovery Optimization?
Date: Fri, 18 Feb 2011 16:06:43 -0800 [thread overview]
Message-ID: <ijn1hs$8nl$1@dough.gmane.org> (raw)
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,
--
Jon Forrest
Research Computing Support
College of Chemistry
173 Tan Hall
University of California Berkeley
Berkeley, CA
94720-1460
510-643-1032
jlforrest@berkeley.edu
next reply other threads:[~2011-02-19 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 0:06 Jon Forrest [this message]
2011-02-19 0:37 ` Recovery Optimization? Mathias Burén
2011-02-19 4:54 ` NeilBrown
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='ijn1hs$8nl$1@dough.gmane.org' \
--to=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).