This bug has been copied from bug #832596 and has been proposed to be backported to 6.3 z-stream (EUS).
Verified these test cases now pass with the latest 6.3.z rpms. SCENARIO (raid4) - [alloc_anywhere] Create a 3-way raid4 volume using only 2 physical devices lvcreate --type raid4 -i 3 -n alloc_anywhere --alloc anywhere -L 150M raid_sanity /dev/sde2:0-1500 /dev/sdf1:0-1500 image0 should be on /dev/sde2 image1 should be on /dev/sdf1 image2 should be on either /dev/sde2 or /dev/sdf1 Deactivating raid alloc_anywhere... and removing SCENARIO (raid5) - [alloc_anywhere] Create a 3-way raid5 volume using only 2 physical devices lvcreate --type raid5 -i 3 -n alloc_anywhere --alloc anywhere -L 150M raid_sanity /dev/sdb1:0-1500 /dev/sdf2:0-1500 image0 should be on /dev/sdb1 image1 should be on /dev/sdf2 image2 should be on either /dev/sdb1 or /dev/sdf2 Deactivating raid alloc_anywhere... and removing SCENARIO (raid6) - [alloc_anywhere] Create a 3-way raid6 volume using only 2 physical devices lvcreate --type raid6 -i 3 -n alloc_anywhere --alloc anywhere -L 150M raid_sanity /dev/sdf2:0-1500 /dev/sdf1:0-1500 image0 should be on /dev/sdf2 image1 should be on /dev/sdf1 image2 should be on either /dev/sdf2 or /dev/sdf1 Deactivating raid alloc_anywhere... and removing 2.6.32-279.el6.x86_64 lvm2-2.02.95-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 lvm2-libs-2.02.95-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 lvm2-cluster-2.02.95-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 udev-147-2.41.el6 BUILT: Thu Mar 1 13:01:08 CST 2012 device-mapper-1.02.74-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 device-mapper-libs-1.02.74-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 device-mapper-event-1.02.74-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 device-mapper-event-libs-1.02.74-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012 cmirror-2.02.95-10.el6_3.1 BUILT: Tue Aug 28 09:31:04 CDT 2012
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-1399.html