Comment 10 for bug 458529

(In reply to comment #0)
> Created an attachment (id=30519) [details]
> output of ls -lR /sys
>
> I have a LVM setup, with one LV in mirrored mode (RAID1) spread over 2 PVs. For
> such a setup, 3 more DM devices are generated: VG-LV_mimage_0, VG-LV_mimage_1
> und VG-LV_mlog. These devices do *not* respresent real LVs, and shouldn't be
> included in dk-disks.

Maybe if these three devices don't represent anything useful, then LVM2 shouldn't expose them as block devices?

But, yes, we need to add proper LVM2 support to DeviceKit-disks / Palimpsest in the same way that we have proper MD (Linux Software RAID) support. This includes untangling the mess that the LVM2 guys like to add an additional three block devices to confuse users. Anyway, that's bug 24672 and I guess we can close either as a duplicate of the other. This bug contains more information so I'm tempted to close bug 24672 as a dupe of this bug.

>
> $ sudo lvs
> LV VG Attr LSize Origin Snap% Move Log
> home ubuntu mwi-ao 465.76G home_mlog
> root ubuntu -wi-ao 10.00G
> swap ubuntu -wi-ao 4.00G
>
> $ sudo lvs -a
> LV VG Attr LSize Origin Snap% Move Log
> home ubuntu mwi-ao 465.76G home_mlog
> [home_mimage_0] ubuntu iwi-ao 465.76G
> [home_mimage_1] ubuntu iwi-ao 465.76G
> [home_mlog] ubuntu lwi-ao 4.00M
> root ubuntu -wi-ao 10.00G
> swap ubuntu -wi-ao 4.00G
>
> To reproduce, create an LVM setup with at least 2 PVs, and change a LV to
> mirrored mode with "sudo lvconvert -m 1 VG/LV".
>