* [linux-lvm] lvm2 + "--type raid1" better than md-Raid + lvm?
@ 2013-07-09 11:24 Oliver Rath
2013-07-09 19:19 ` matthew patton
0 siblings, 1 reply; 2+ messages in thread
From: Oliver Rath @ 2013-07-09 11:24 UTC (permalink / raw)
To: linux-lvm
Hi list,
it is better using two lvm-disks with --type=raid1 option or is it the
same quality like creating a raid1-device (via mdadm) and putting a lvm2
on it?
Tfh!
Oliver
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-lvm] lvm2 + "--type raid1" better than md-Raid + lvm?
2013-07-09 11:24 [linux-lvm] lvm2 + "--type raid1" better than md-Raid + lvm? Oliver Rath
@ 2013-07-09 19:19 ` matthew patton
0 siblings, 0 replies; 2+ messages in thread
From: matthew patton @ 2013-07-09 19:19 UTC (permalink / raw)
To: LVM general discussion and development
> it is better using two lvm-disks with --type=raid1 option or is it the
> same quality like creating a raid1-device (via mdadm) and
> putting a lvm2 on it?
I think most people go with the latter. Though of course the former gives you much more flexibility in how you assemble raid sets.
I was playing with a script to build 3Par-like (and I use that term loosely) RAID arrays out of scattered extents from a pool (say 16) disks in a volume group and optionally across multiple such volume groups. LVM in this case was used for "soft partition" sizing of the individual MD components, and then of course you can layer LVM on top of the MD device for end-user consumption. The idea being RAID rebuild was a distributed matter and the impact would be spread across a lot of spindles instead of causing a very concentrated heat map.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-07-09 19:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-09 11:24 [linux-lvm] lvm2 + "--type raid1" better than md-Raid + lvm? Oliver Rath
2013-07-09 19:19 ` matthew patton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).