From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Ramon Hofer <ramonhofer@bluewin.ch>, linux-raid@vger.kernel.org
Subject: Re: Enlarging device of linear array
Date: Sun, 09 Jun 2013 06:52:09 -0500 [thread overview]
Message-ID: <51B46C69.5030205@hardwarefreak.com> (raw)
In-Reply-To: <20130609164728.6c21a2f6@natsu>
On 6/9/2013 5:47 AM, Roman Mamedov wrote:
> On Sat, 8 Jun 2013 20:18:10 +0200
> Ramon Hofer <ramonhofer@bluewin.ch> wrote:
>
>> My home server with a linear raid (md0) containing three raid5 (md1,
>> md2, md3) is still working wonderfully. Thanks again Stan!
>>
>> Now I'm planning to add a fourth raid5 to the linear array.
>
> You should have used LVM instead of md linear to join your RAIDs into a single
> block device. LVM allows placing a single logical volume over physical extents
> placed in all sorts of non-contiguous, fragmented, overlapping fashions. You
> could also transparently migrate portions of those physical extents between
> physical arrays without even having to unmount the filesystem that you have on
> the LV.
FYI, I designed this architecture for Ramon. He CC's linux-raid as a
courtesy so that others may learn from his experience with it, and in
the event I may be unavailable.
Yes, LVM could have been used. It was specifically not used because
Ramon is using XFS, which is stripe aligned to each constituent RAID5
array, which each contain a fixed set of allocation groups. I'm sure
you understand the negative performance implications involved when
breaking alignment with parity RAID, or moving parts of an AG from one
disk or array to another.
--
Stan
prev parent reply other threads:[~2013-06-09 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 18:18 Enlarging device of linear array Ramon Hofer
2013-06-09 8:31 ` Stan Hoeppner
2013-06-09 10:38 ` Sam Bingner
2013-06-10 16:58 ` Ramon Hofer
2013-06-09 10:47 ` Roman Mamedov
2013-06-09 11:52 ` Stan Hoeppner [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=51B46C69.5030205@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=ramonhofer@bluewin.ch \
--cc=rm@romanrm.ru \
/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