From: Neil Brown <neilb@suse.de>
To: linbloke <linbloke@fastmail.fm>
Cc: linux-raid@vger.kernel.org
Subject: Re: Auto Rebuild on hot-plug
Date: Wed, 31 Mar 2010 12:35:34 +1100 [thread overview]
Message-ID: <20100331123534.1b86c77d@notabene.brown> (raw)
In-Reply-To: <4BAC56FE.1000009@fastmail.fm>
On Fri, 26 Mar 2010 17:41:02 +1100
linbloke <linbloke@fastmail.fm> wrote:
> Hi Neil,
>
> I look forward to being able to update my mdadm.conf with the paths to
> devices that are important to my RAID so that if a fault were to develop
> on an array, then I'd be really happy to fail and remove the faulty
> device, insert a blank device of sufficient size into the defined path
> and have the RAID auto restore. If the disk is not blank or too small,
> provide a useful error message (insert disk of larger capacity, delete
> partitions, zero superblocks) and exit. I think you do an amazing job
> and it worries me that you and the other contributors to mdadm could
> spend your valuable time trying to solve problems about how to cater for
> every metadata, partition type etc when a simple blank device is easy to
> achieve and could then "Auto Rebuild on hot-plug".
:-)
One the one hand, we should always look beyond the immediate problem we are
tring to solve in order to see the big picture and make sure the solution we
choose doesn't cut us off from solving other more general problems when they
arrive.
On the other hand, we don't want to expand the scope so much that we end up
biting off more than we can chew.
A general design with a specific implementation is probably a good target....
Thanks,
NeilBrown
>
> Perhaps as we nominate a spare disk, we could nominate a spare path. I'm
> certainly no expert and my use case is simple (raid 1's and 10's) but it
> seems to me a lot of complexity can be avoided for the sake of a blank disk.
>
> Cheers,
> Josh
>
>
>
next prev parent reply other threads:[~2010-03-31 1:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 0:35 Auto Rebuild on hot-plug Neil Brown
2010-03-25 2:47 ` Michael Evans
2010-03-31 1:18 ` Neil Brown
2010-03-31 2:46 ` Michael Evans
2010-03-25 8:01 ` Luca Berra
2010-03-31 1:26 ` Neil Brown
2010-03-31 6:10 ` Luca Berra
2010-03-25 14:10 ` John Robinson
2010-03-31 1:30 ` Neil Brown
2010-03-25 15:04 ` Labun, Marcin
2010-03-27 0:37 ` Dan Williams
2010-03-29 18:10 ` Doug Ledford
2010-03-29 18:36 ` John Robinson
2010-03-29 18:57 ` Doug Ledford
2010-03-29 22:36 ` John Robinson
2010-03-29 22:41 ` Dan Williams
2010-03-29 22:46 ` John Robinson
2010-03-29 23:35 ` Doug Ledford
2010-03-30 12:10 ` John Robinson
2010-03-30 15:53 ` Doug Ledford
2010-04-02 11:01 ` John Robinson
2010-03-29 21:36 ` Dan Williams
2010-03-29 23:30 ` Doug Ledford
2010-03-30 0:46 ` Dan Williams
2010-03-30 15:23 ` Doug Ledford
2010-03-30 17:47 ` Labun, Marcin
2010-03-30 23:47 ` Dan Williams
2010-03-30 23:36 ` Dan Williams
2010-03-31 4:53 ` Neil Brown
2010-03-26 6:41 ` linbloke
2010-03-31 1:35 ` Neil Brown [this message]
2010-03-26 7:52 ` Majed B.
2010-03-31 1:42 ` Neil Brown
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=20100331123534.1b86c77d@notabene.brown \
--to=neilb@suse.de \
--cc=linbloke@fastmail.fm \
--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).