Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On the lvconvert(8) man page it says:

--type SegmentType
       Used to convert a logical volume to another segment type  or  to
       explicitly  state  the  desired  RAID1 segment type ("mirror" or
       "raid1") when converting a linear logical  volume  to  a  mirror
       with the '-m' argument.

But what exactly is the difference between "mirror" and "raid1"?

share|improve this question
up vote 5 down vote accepted

I have not yet tried the new LVM segment types, but the overview is that they are support for the Linux MD RAID personalities in LVM. That is, they are RAID levels 1, 5, 6 etc. using the MD code with the eventual goal of removing the duplicate functionality of LVM's mirroring and having both MD and LVM use the same code.

This is very new stuff so may not be appropriate for a production setup yet.

For example it is still considered a technology preview in RHEL 6.2:

share|improve this answer
So this is similar to creating a RAID with mdadm that uses multiple LVs as disks just with tighter integration into LVM? – Julian Apr 14 '12 at 16:01
The point with RAID is to use multiple physical disks for gaining fault-tolerance and/or improved performance. mdadm on the top of LVM doesn't make much sense, but LVM on the top of mdadm was considered "best practice" when not having a hardware raid. Now that LVM supports RAID out of the box, it seems preferable (due to the flexibility offered) to rather use the RAID-support in LVM, but I suppose mdadm (or hardware RAID) is still needed for a bootable fault-tolerant setup. – tobixen Oct 20 '12 at 11:33

The practical difference is that the 'raid1' mirror segment type always stores its logs (in fact, metadata subvolumes) on-disk on the same PVs as the lv being mirrored. You no-longer need a third pv for the log, or to store the log in-memory, and consequently the --corelog and --mirrorlog disk/core/mirrored options to lvconvert are not applicable to the raid1 mirror segment type.

Another practical difference is that you need an additional 1 PE on both PVs (original and mirror) in order to store the log(s), allocated when the mirror is created. If you see an error like 1 extents needed, but only 0 available when trying to create a raid1 type mirror with lvconvert, this is probably a failure to allow 1 PE additional space for the log on each of the PVs.

Since about September 2013, raid1 has been the default mirror segment type in lvm2.

share|improve this answer

Your Answer


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.