From: Scott Serr <serrs@theserrs.net>
To: Erik@echohome.org,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm over raid5 - sizes
Date: Tue, 01 Mar 2005 09:02:54 -0700 [thread overview]
Message-ID: <4224922E.8070503@theserrs.net> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAiKro/zVEU02Xw5blW4RJy8KAAAAQAAAA3hs8l0VXbU2EEHXI+Ey1iwEAAAAA@echohome.org>
Oh wow... I thought EMVS was a LVM2 "equivalent." Can't really give
you any ideas about EMVS without doing some reading, but the "RAID5
region" sounds neat.
My Experience:
I've been using LVM2 ontop of software RAID5 for over a year. I've been
happy with it. It seems a little slow... but I don't care too much. I
know atleast some other people are doing it, and it does fit my needs.
I've gone through the whole "grow" process twice now. It is time
consuming to grow the disk, but you don't have to sit and watch... and
you can have the system live if you wish. A "pvmove /dev/md0 /dev/md3"
takes about 8 hours with their sizes about 174GB.
If you can afford 1 hot spare (like your other message said) you might
want to go with RAID1, it would be faster.
Erik Ohrnberger wrote:
>Well, I have a similar problem/desire.
>
>I want to have RAID5 for redundancy/reliability. But I want to be able to
>resize the file system stored on the RAID5 array, as well as being able to
>add and remove hard disks to either increase/decrease available storage.
>
>What would be your recommendation for a configuration?
>
>At the moment, I'm considering using EVMS with its RAID5 regions, and put
>LVM2 on top of it.
>
>Thanks in advance,
> Erik.
>
>
>
>>-----Original Message-----
>>From: linux-lvm-bounces@redhat.com
>>[mailto:linux-lvm-bounces@redhat.com] On Behalf Of Sam Vilain
>>Sent: Monday, February 28, 2005 12:11 AM
>>To: LVM general discussion and development
>>Subject: Re: [linux-lvm] lvm over raid5 - sizes
>>
>>
>>Scott Serr wrote:
>>
>>
>>>I have alot of ideas going through my head. Here is my situation:
>>>
>>>I've had 5 IDEs with 4 partitions each. Each partition is
>>>
>>>
>>in a RAID5
>>
>>
>>>md:stripped.
>>>md0 = hda5, hdb5, hdc5, hdd5, hde5
>>>md1 = hda6, hdb6, hdc6, hdd6, hde6
>>>md2 = hda7, hdb7, hdc7, hdd7
>>>md3 = hda8, hdb8, hdc8, hdd8
>>>
>>>md0-3 are in an LVM2 volume group. This makes it really nice when
>>>expanding or adding another disk because I just pull say
>>>
>>>
>>md3 out of the
>>
>>
>>>volume group... rebuild md3 bigger and then add it back.
>>>I just upgraded, replacing hde with a bigger disk and while
>>>
>>>
>>the pvmoves
>>
>>
>>>are taking FOREVER... I thought what is the right size for
>>>
>>>
>>the RAID5
>>
>>
>>>chunk-size?
>>>
>>>I have chunk-size = 128k right now.
>>>
>>>The pv extents size is (always?) 4MB.
>>>
>>>Am I just shooting myself in the foot by not making my RAID
>>>
>>>
>>chunk size
>>
>>
>>>atleast 1MB? Can someone give me a reason to increase it?
>>>
>>>
>>You're shooting yourself in the foot with RAID 5 and a crazy
>>setup like this in the first place. I sure hope this isn't
>>for a production box :)
>>
>>Just get more disks and use RAID 1. It's faster, simpler,
>>and more robust. You can still do all of the tricks that
>>you're looking for.
>>
>>Hey, maybe one of the disks has failed. Standard RAID 5
>>behaviour as designed in this case is to slow to a crawl.
>>Alternatively maybe you're just experiencing what is known in
>>the 'biz as "The Butterfly Effect".
>>
>>With most striping, keep the chunk size as large as possible.
>> It's a real waste to spend 10ms waiting for the disk platter
>>to rotate, and then only read 128kB of data. Set it as high
>>as possible.
>>--
>>Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13
>>(include my PGP key ID in personal replies to avoid spam filtering)
>>
>>_______________________________________________
>>linux-lvm mailing list
>>linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm
>>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>
>>
>>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@redhat.com
>https://www.redhat.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
next prev parent reply other threads:[~2005-03-01 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 23:13 [linux-lvm] lvm over raid5 - sizes Scott Serr
2005-02-28 5:10 ` Sam Vilain
2005-02-28 5:43 ` Erik Ohrnberger
2005-03-01 16:02 ` Scott Serr [this message]
2005-02-28 6:53 ` Scott Serr
2005-03-01 1:47 ` Sam Vilain
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=4224922E.8070503@theserrs.net \
--to=serrs@theserrs.net \
--cc=Erik@echohome.org \
--cc=linux-lvm@redhat.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.