Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I think I remember making some mirrors years ago with LVM, and I don't remember this "log" thing. Or maybe I made the mirror with mdadm and put LVM on top. That must be it.

  1. What is the LVM log for if it is just a mirror? What is stored there? What is it's purpose? Is using "--mirrorlog core" bad? What's the down side? I don't want to have to have another partition for logs if I don't have to.

  2. Any recommendations on using either technology? Even if I make the mirror with mdadm, I'll use LVM on top of that. So, in that case, maybe it's better to have the whole setup built with LVM...? Would that take more a performance hit or less?

The disks are for storing Xen domU "disks".

Sorry for the complex not-to-the-point "question".

Ideas and suggestions and links are most welcome. Thanks!

share|improve this question
    
md seems to perform better for mirror operations when compared to lvm. See serverfault.com/questions/80134/linux-md-vs-lvm-performance –  Zoredache Mar 27 '10 at 7:33
1  
LVM mirroring was meant for a different purpose. While you can use it to "mirror" the way MD does, it really is used for cloning volumes. See serverfault.com/questions/97845/lvm-mirroring-vs-raid1 –  Avery Payne Jun 3 '10 at 23:41
1  
If it's meant for cloning, then why does it require three volumes? –  d-_-b Jun 4 '10 at 0:02
add comment

5 Answers

up vote 5 down vote accepted

Personally I always go MD+LVM. It is faster (MD can do parallel reads in RAID1) and it requires only 2 disks (if you do not want to rebuild the mirror after every reboot) and MD is designed just to do RAID, and it does it very well. It is also more flexible.

Also I have been burned by LVM. In one case it was LVM striping on HP-UX, (should not happen w/ LVM2 in Linux), and I could not extend the LV because the extension had to have the exact same number of stripes. It seems reasonable, but sometimes ...

Another time it was with mirroring (LVM2 in Linux this time), but now I cannot remember if LVM refused to take a snapshot of a mirrored LV or to extend it, effectively negating the benefit for having LVM in the first place (we did it in the end, but involved using lvconvert back and forth).

share|improve this answer
    
Thanks! I think I'll go with LVM on top of MD. It looks as if there are some issues with MD's autodetect. (raid.wiki.kernel.org/index.php/RAID_Boot) I kind of wanted to mirror my entire system (swap, boot, /, var, home, usr). So I'll have to look into something other than autodetect. –  d-_-b Mar 28 '10 at 2:06
    
Yes, autodetect is a nice idea in principle, but it gives all sort of headaches. I have a set up with iSCSI+multipath+MD+LVM... and autodetect is... interesting, but useless in this case. –  Dan Andreatta Mar 28 '10 at 8:19
add comment

these are two different concepts:

  • LVM is as the name says it for volume management. Think of it as a mechanism to combine multiple volumes into one (yeah you can say it's like raid0), resizing them, live resizing, creating snapshots.
  • MD is for RAID management. Add multiple devices into one metadevice, make this metadevice highly available by using raid1, 5, 10, etc...

LVM operates on storage devices be it metadevices, or devices presented by the raid controller, or just plain disks.

MD operates on disks (yeah you can also use disks presented by the raid controller, but what's the point?..

LVM is not for making your storage highly available. And likewise MD is not for volume management...

Hope this helps :)

share|improve this answer
1  
I understand what they are. However, if you read the man page for lvcreate, it says it can create mirrors. I guess this is a bit of toy for now? –  d-_-b Mar 28 '10 at 2:07
1  
imho yes. i can't see any good use for it at least for now. not only it's a mirror on a volume (rather than device) level, it's also bit "interesting" how it's created, for example if you need 2 way mirror (as in original+copy) you need to have 3 volumes - one for each side of mirror + log volume. but then again - imho. :) –  rytis Mar 28 '10 at 18:23
add comment

LVM came from other UNIX system types. I used it on HPUX which did not have the MD layer of Linux when I worked on it 10 years ago, not sure about now. Under those circumstances LVM mirroring becomes useful in a situation where hardware RAID is not available.

share|improve this answer
    
I just found it odd that an LVM mirror needs more that one volume. What kind of a mirror is that? –  d-_-b Jul 4 '11 at 15:12
1  
@toor the third volume is used to store a write-ahead log for the mirror, basically to keep track of what needs to be resynced after an abrupt stop. On MD, this is normally stored in a reserved part of the two disks. –  poolie Aug 18 '12 at 3:08
add comment

When a mirrored pair is abruptly shut down, in any system, there may be some blocks that have been written to one device but not yet to the other. Conceivably with reordering IO paths there are some blocks that have been written to A but not B, and some written to B but not yet to A.

When the machine restarts, it needs to make the devices consistent. Just having the two devices alone is not enough: it wouldn't know which blocks are inconsistent and it wouldn't know which version was more recent.

So the mirror software needs to store a bit of metadata to keep track of this. This is called the "write-intent log".

md normally stores it in some reserved space inside the device itself, though you can also choose to store it on a separate device. (This is one reason why md mirrors are slightly smaller than the basis devices.

LVM mirrors can only store the write-extent log externally, which as you note is a bit annoying for the typical case where you have exactly two physical disks. I believe you do still have the choice to store it on a different partition on the same physical device, but that's still inconvenient.

The purpose of the LVM mirror log, as I understand it, is to keep track of blocks that have been written to one device but not yet to the other.

share|improve this answer
add comment

with the -mirrorlog mirrored and the -alloc anywhere option, with two disks, you get two 4M mirror logs, one on each disk. I'm annoyed that I have to override the policy for what seems like a most common situation, but oh well.

LVM on Linux is not related to the thing on HP-UX or AIX, just has the same userspace commands. LVM on Linux internally uses the DM system, and therefore uses all the same code as MD. At this point, I see no advantage of LVM over MD. For partitions which you want fast and do not care about backups for (e.g. swap partitions for guest VMs), LVM gives you option of whether you want those mirrored or not, or whether stripping is better.

And, it's way easier to add a disk to LVM than MD.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.