From: John Robinson <john.robinson@anonymous.org.uk>
To: Doug Ledford <dledford@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
"Labun, Marcin" <Marcin.Labun@intel.com>,
Neil Brown <neilb@suse.de>,
"Hawrylewicz Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
Bill Davidsen <davidsen@tmr.com>
Subject: Re: Auto Rebuild on hot-plug
Date: Mon, 29 Mar 2010 23:36:39 +0100 [thread overview]
Message-ID: <4BB12B77.8030902@anonymous.org.uk> (raw)
In-Reply-To: <4BB0F820.4030707@redhat.com>
On 29/03/2010 19:57, Doug Ledford wrote:
> On 03/29/2010 02:36 PM, John Robinson wrote:
[...]
>> Yes, but do create the partition(s), boot sector, etc and set up the
>> spare(s).
>
> Really, we should never have to do this in the situation I listed: aka
> no degraded arrays exist. This implies that if you had a raid1 /boot
> array, that it's still intact. So partitioning and setting up boot
> loaders doesn't make sense as the new disk isn't going in to replace
> anything. You *might* want to add it to the raid1 /boot, but we don't
> know that so doing things automatically doesn't make sense.
Actually I've just recently had the scenario where it would have made
perfect sense. I hooked up the RAID chassis SATA[0-4] ports to the RAID
chassis and put 3 drives in the first 3 slots. Actually it turned out
I'd wired it up R-L not L-R so if I'd added a new drive in one of the
two right-hand slots it would have turned up as sda on the next boot.
OK, to some extent that's me being stupid, but at the same time I
correctly hooked up the first 5 SATA ports to the hot-swap chassis and
would want them considered the same group etc.
Cheers,
John.
next prev parent reply other threads:[~2010-03-29 22:36 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 [this message]
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
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=4BB12B77.8030902@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=Marcin.Labun@intel.com \
--cc=dan.j.williams@intel.com \
--cc=davidsen@tmr.com \
--cc=dledford@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.