From: "Peter Kovari" <peter@kovari.priv.hu>
To: linux-raid@vger.kernel.org
Subject: RE: A few questions regarding RAID5/RAID6 recovery
Date: Tue, 26 Apr 2011 18:13:49 +0200 [thread overview]
Message-ID: <000301cc042c$edcfc330$c96f4990$@priv.hu> (raw)
In-Reply-To: <ip5rnd$g96$1@dough.gmane.org>
-----Original Message-----
From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of David Brown
Sent: Tuesday, April 26, 2011 9:22 AM
To: linux-raid@vger.kernel.org
Subject: Re: A few questions regarding RAID5/RAID6 recovery
> You are not alone in these concerns. A couple of months ago there was a
> long thread here about a roadmap for md raid. The first two entries are
> a "bad block log" to allow reading of good blocks from a failing disk,
> and "hot replace" to sync a replacement disk before removing the failing
> one. Being on a roadmap doesn't mean that these features will make it
> to md raid in the near future - but it does mean that there are already
> rough plans to solve these problems.
> <http://neil.brown.name/blog/20110216044002>
Thank you David, this explains a lot. I hope we'll see this some day implemented.
Can you comment on my first question too please? Basically i'm just curious to know if there is a way to stop and restart the rebuilding process (and change/re-create the array in between them).
Btw, i read somewhere, that "--stop", then "--create --assume-clean" on an array works only on v0.9 superblocks, because v1.x overwrites existing data during create. It doesn't make sense for me - but i'm not sure -, so is this true? If not, then is it enough to use the same suberblock version for "--create" to make this work without data loss?
Thanks,
Peter
prev parent reply other threads:[~2011-04-26 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 17:47 A few questions regarding RAID5/RAID6 recovery Kővári Péter
2011-04-25 19:51 ` Ryan Wagoner
2011-04-26 7:21 ` David Brown
2011-04-26 16:13 ` Peter Kovari [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='000301cc042c$edcfc330$c96f4990$@priv.hu' \
--to=peter@kovari.priv.hu \
--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).