From: Scott Serr <serrs@theserrs.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Software raid on top of lvm logical volume
Date: Sun, 31 Oct 2004 23:46:00 -0700 [thread overview]
Message-ID: <4185DBA8.7060605@theserrs.net> (raw)
In-Reply-To: <41851771.4060203@markus.org>
I've done something like Markus explained. I had this email ready to go
a couple days ago, but the compose window was hidden for a while... I
hope it's not too stale for the original poster of this thread:
2.4.26 with latest LVM2 works well. I did something crazy, alot of
people probably don't understand why.
I have software RAID5.
md0 = hda5 hdb5 hdc5 hdd5 hde5
md1 = hda6 hdb6 hdc6 hdd6 hde6
md2 = hda7 hdb7 hdc7 hdd7
md3 = hda8 hdb8 hdc8 hdd8
Then I have just one big vgdata and one lvdata.
Why would I want to do this? I couldn't find any other way to have
redundancy and be flexible. If I replace a physical disk with a larger
one, for instance hde needs to be bigger so I can make md2 and md3
stretch across that disk too... then I am able to do pvmove from md2 to
a scratch disk, recreate md2 across hda7-hde7, then pvmove back.
-Scott
Markus Baertschi wrote:
> Michael T. Babcock wrote:
>
>>
>> I've thought about this numerous times -- there is the distinct
>> resizing advantage. Namely, if I create a software RAID partition, I
>> can't resize it afterward without destroying it. I have for example,
>> on occasion, had three disks set up where 1/3 of each was devoted to
>> a RAID-0 very fast striping set for data transfers that had to be
>> fast but if they were lost it wasn't critical, and 2/3 was set up as
>> RAID-5 for reliability of another set of data.
>>
>> I understand this may not be optimal in some situations, but some of
>> us don't have thousands of dollars for SCSI HW RAID controllers.
>
>
> You can make life easier by creating several raid arrays on the same
> disks and tie them together with LVM.
> For example split your three 160GB drives into 4 partitions each and
> create a raid over the three disks.
>
> sda -> sda1+sda2+sda3+sda4, etc.
> md0 = sda1+sdb1+sdc1, md1=sda2+sdb2+sdc2, etc.
>
> Markus
>
next prev parent reply other threads:[~2004-11-01 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 22:02 [linux-lvm] Software raid on top of lvm logical volume Eric Monjoin
2004-10-28 1:17 ` Theo Van Dinter
2004-10-28 6:01 ` Eric Monjoin
2004-10-28 6:35 ` Luca Berra
2004-10-28 19:17 ` [linux-lvm] " Peter T. Breuer
2004-11-01 16:01 ` Michael T. Babcock
2004-11-01 16:51 ` Erik Ohrnberger
2004-11-01 22:03 ` Clint Byrum
2004-11-01 22:07 ` Theo Van Dinter
2004-11-02 15:46 ` Michael T. Babcock
2004-10-28 18:54 ` [linux-lvm] " Michael T. Babcock
2004-10-30 16:55 ` [linux-lvm] " Peter T. Breuer
2004-10-30 17:10 ` [linux-lvm] What is the best way to configure LVM + RAID? Erik Ohrnberger
2004-10-31 17:34 ` [linux-lvm] " Peter T. Breuer
2004-10-30 17:27 ` [linux-lvm] Software raid on top of lvm logical volume Theo Van Dinter
2004-10-30 19:22 ` [linux-lvm] LVM DISK DIE "KieZz"
2004-10-31 16:48 ` [linux-lvm] Software raid on top of lvm logical volume Markus Baertschi
2004-11-01 6:46 ` Scott Serr [this message]
2004-11-01 15:38 ` Michael T. Babcock
2004-11-01 17:02 ` [linux-lvm] " Peter T. Breuer
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=4185DBA8.7060605@theserrs.net \
--to=serrs@theserrs.net \
--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.