THIS IS THE RHEL4 VERSION OF BZ 463272. Description of problem: If you attempt to down convert a mirror as well as convert it from core to disk log on the same cmd line, the disk log convert option will be dropped (not executed). However if you attempt to down convert a mirror as well as convert it from disk to core log on the same cmd line, it will work. If you run the "half completed" cmd line that didn't do the disklog convert initially a second time, then it'll work since the down convert has already happened. [root@grant-01 ~]# lvs -a -o +devices LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices mirror grant Mwi-a- 1.00G 100.00 mirror_mimage_0(0),mirror_mimage_1(0),mirror_mimage_2(0) [mirror_mimage_0] grant iwi-ao 1.00G /dev/sdb1(0) [mirror_mimage_1] grant iwi-ao 1.00G /dev/sdb2(0) [mirror_mimage_2] grant iwi-ao 1.00G /dev/sdb3(0) [root@grant-01 ~]# lvconvert --mirrorlog disk -m 1 grant/mirror Logical volume mirror converted. [root@grant-01 ~]# lvs -a -o +devices LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices mirror grant Mwi-a- 1.00G 18.75 mirror_mimage_0(0),mirror_mimage_1(0) [mirror_mimage_0] grant Iwi-ao 1.00G /dev/sdb1(0) [mirror_mimage_1] grant Iwi-ao 1.00G /dev/sdb2(0) ## Note the above mirror still has an in-core log. Version-Release number of selected component (if applicable): 2.6.9-78.0.4.ELsmp lvm2-2.02.37-3.el4 BUILT: Thu Jun 12 10:09:19 CDT 2008 lvm2-cluster-2.02.37-3.el4 BUILT: Thu Jun 12 10:22:07 CDT 2008 device-mapper-1.02.25-2.el4 BUILT: Mon Jun 9 09:28:41 CDT 2008 cmirror-1.0.1-1 BUILT: Tue Jan 30 17:28:02 CST 2007 cmirror-kernel-2.6.9-43.4.el4_7.3 BUILT: Tue Sep 16 15:17:13 CDT 2008 How reproducible: Everytime
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
I think the right way to handle this in RHEL 4 is to document the limitation, rather than take any risk that a fix may introduce a regression. I'll close this and set the flag requesting a release note. Petr, would you investigate the source of the problem, to see whether it may effect other command lines that specificy multiple operations? Once you understand the cause, please draft a release note (in the field above) that describes which type of combined operations do not execute completely. Then, maybe fix it in RHEL 5 BZ 463272? :)