From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Another take on replacing failed raid drives
Date: Fri, 26 Mar 2010 18:59:26 +0000 [thread overview]
Message-ID: <4BAD040E.2010304@anonymous.org.uk> (raw)
In-Reply-To: <4BACCD8B.8040705@xs4all.nl>
On 26/03/2010 15:06, John Hendrikx wrote:
> Bill Davidsen wrote:
>> I stumbled on this description of replacing a drive in a raid array. I
>> share it because different takes on a subject are usesful, and because
>> he had multiple arrays using partitions of the failed drive, rather
>> than a partitioned array.
>>
>> http://blogs.techrepublic.com.com/opensource/?p=1368
>>
> I do that too (multiple arrays using partitions). My reason for that is
> to make future upgrades less painful as it is possible to just copy and
> drop one array at a time.
I do that too, but my reason is that the arrays are different types. For
example, first partitions make RAID-1 for /boot, second partitions
RAID-1 or RAID-10 swap, third partitions RAID-5 or RAID-6 filesystem (or
several over LVM).
Cheers,
John.
prev parent reply other threads:[~2010-03-26 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 17:06 Another take on replacing failed raid drives Bill Davidsen
2010-03-26 15:06 ` John Hendrikx
2010-03-26 18:59 ` John Robinson [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=4BAD040E.2010304@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--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 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.