public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dmraid, mdraid, lvm, btrfs, what?
Date: Tue, 29 Nov 2011 20:23:12 +0100	[thread overview]
Message-ID: <4ED53120.2030209@binarywings.net> (raw)
In-Reply-To: <CA+czFiDO6cqs=2LWRbZWg_v2KDaCbu+JaSbB4_gGpY7BFdvJZg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

Am 29.11.2011 19:39, schrieb Michael Mol:
> On Tue, Nov 29, 2011 at 1:20 PM, Florian Philipp <lists@binarywings.net> wrote:
>> Am 29.11.2011 14:44, schrieb Michael Mol:
>>> On Tue, Nov 29, 2011 at 2:07 AM, Florian Philipp <lists@binarywings.net> wrote:
>>>> Am 29.11.2011 05:10, schrieb Michael Mol:
>>>>> I've got four 750GB drives in addition to the installed system drive.
>>>>>
>>>>> I'd like to aggregate them and split them into a few volumes. My first
>>>>> inclination would be to raid them and drop lvm on top.  I know lvm well
>>>>> enough, but I don't remember md that well.
>>>>>
>>>>> Since I don't recall md well, and this isn't urgent, I figure I can look
>>>>> at the options.
>>>>>
[...]
>>>> What kind of RAID level do you want to use, 10 or 5? You
>>>> can also split it: Use a smaller RAID 10 for performance-critical
>>>> partitions like /usr and the more space-efficient RAID 5 for bulk like
>>>> videos. You can handle this with one LVM volume group consisting of two
>>>> physical volumes. Then you can decide on a per-logical-volume basis
>>>> where it should allocate space and also migrate LVs between the two PVs.
>>>
>>> Since I've got four disks for the pool, I was thinking raid10 with lvm
>>> on top, and a single lvm pv above that.
>>>
>>
>> Yeah, that would also be my recommendation. But if storage efficiency is
>> more relevant, RAID-5 with 4 disks brings you 750GB more usable storage.
>>
>>
> 
> It looks like I'll want to try two different configurations. RAID5 and
> RAID10. Not for different storage requirements, but I want to see
> exactly what the performance drop is.
> 
> I wish lvm striping supported data redundancy. But, then, I wish btrfs
> was ready...
> 

Just out of curiosity: What happens if you do `lvcreate --mirrors 1
--stripes 2 ...`? Does it create something similar to a RAID-10 or does
it simply fail?

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-11-29 19:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  4:10 [gentoo-user] dmraid, mdraid, lvm, btrfs, what? Michael Mol
2011-11-29  7:07 ` Florian Philipp
2011-11-29 13:44   ` Michael Mol
2011-11-29 18:20     ` Florian Philipp
2011-11-29 18:39       ` Michael Mol
2011-11-29 19:23         ` Florian Philipp [this message]
2011-11-29 19:27           ` Michael Mol
2011-11-29 17:35   ` [gentoo-user] " Jack Byer
2011-11-29 14:10 ` [gentoo-user] " Mark Knecht
2011-11-29 16:53   ` Michael Mol
2011-11-29 19:02     ` Jarry
2011-11-29 19:34       ` Mark Knecht
2011-11-29 19:44         ` Michael Mol

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=4ED53120.2030209@binarywings.net \
    --to=lists@binarywings.net \
    --cc=gentoo-user@lists.gentoo.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