From: John Robinson <john.robinson@anonymous.org.uk>
To: "Majed B." <majedb@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Full use of varying drive sizes?
Date: Wed, 23 Sep 2009 09:20:32 +0100 [thread overview]
Message-ID: <4AB9DA50.5040007@anonymous.org.uk> (raw)
In-Reply-To: <70ed7c3e0909220607y692e15a2s64aac9bd729422ef@mail.gmail.com>
On 22/09/2009 14:07, Majed B. wrote:
> When I first put up a storage box, it was built out of 4x 500GB disks,
> later on, I expanded to 1TB disks.
>
> What I did was partition the 1TB disks into 2x 500GB partitions, then
> create 2 RAID arrays: Each array out of partitions:
> md0: sda1, sdb1, sdc1, ...etc.
> md1: sda2, sdb2, sdc2, ...etc.
>
> All of those below LVM.
>
> This worked for a while, but when more 1TB disks started making way
> into the array, performance dropped because the disk had to read from
> 2 partitions on the same disk, and even worse: When a disk fail, both
> arrays were affected, and things only got nastier and worse with time.
Sorry, I don't quite see what you mean. Sure, if half your drives are
500GB and half are 1TB, and you therefore have 2 arrays on the 1TB
drives, with the arrays as PVs for LVM, and one filesystem over the lot,
you're going to get twice as many read/write ops on the larger drives,
but you'd get that just concatenating the drives with JBOD. I wasn't
suggesting you let LVM stripe across the arrays, though - that would be
performance suicide.
> I would not recommend that you create arrays of partitions that rely
> on each other.
Again I don't see what you mean by "rely on each other", they're just
PVs to LVM.
Cheers,
John.
next prev parent reply other threads:[~2009-09-23 8:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 11:24 Full use of varying drive sizes? Jon Hardcastle
2009-09-22 11:52 ` Kristleifur Daðason
2009-09-22 12:58 ` John Robinson
2009-09-22 13:07 ` Majed B.
2009-09-22 15:38 ` Jon Hardcastle
2009-09-22 15:47 ` Majed B.
2009-09-22 15:48 ` Ryan Wagoner
2009-09-22 16:04 ` Robin Hill
2009-09-23 8:20 ` John Robinson [this message]
2009-09-23 10:15 ` Tapani Tarvainen
2009-09-23 12:42 ` Goswin von Brederlow
2009-09-22 13:05 ` Tapani Tarvainen
2009-09-23 10:07 ` Goswin von Brederlow
2009-09-23 14:57 ` Jon Hardcastle
2009-09-23 20:28 ` Full use of varying drive sizes?---maybe a new raid mode is the answer? Konstantinos Skarlatos
2009-09-23 21:29 ` Chris Green
2009-09-24 17:23 ` John Robinson
2009-09-25 6:09 ` Neil Brown
2009-09-27 12:26 ` Konstantinos Skarlatos
2009-09-28 10:53 ` Goswin von Brederlow
2009-09-28 14:10 ` Konstantinos Skarlatos
2009-10-05 9:06 ` Goswin von Brederlow
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=4AB9DA50.5040007@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=majedb@gmail.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.