Description of problem: Data alignment value is always taken as 1024k on RHEL7. Data alignment value should be calculated based on RAID6, RAID10 and RAID0 and should be passed to pvcreate appropriately. Version-Release number of selected component (if applicable): ovirt-engine-3.6.0-0.0.master.20150420232310.gite30f655.el6.noarch How reproducible: Always. Steps to Reproduce: 1. Add a RHEL7 host to console. 2. Now select the device and say create brick. 3. once the brick is created, run the command to check the data alignment value. pvs -o +pe_start <disk> Actual results: Data alignment value is always passed as 1024k Expected results: Data alignment should be caluclated based on RAID0,RAID6 and RAID10 and should be passed appropriately. Additional info:
Tim, Can you update with blivet bug dependency?
ovirt-3.6.0-3 release
Tested with RHEV 3.6.2.6 and RHGS Nightly ( glusterfs-3.7.5-17.el7rhgs ) verified this with virtual disks as of now and provided all the necessary details required. When a brick is created on RAID6 (on RHEL7) with 12 disks and 128KB stripe size below is the data alignment value. On RAID6: ---------------- ---------------- [root@dhcp37-136 ~]# pvs -o +pe_start /dev/vde PV VG Fmt Attr PSize PFree 1st PE /dev/vde RHS_vg4 lvm2 a-- 100.00g 5.00m 1.25m When a brick is created on RAID10 (on RHEL7) with 10 disks and 256KB stripe size below is the data alignment value. On RAID10: -------------- -------------- [root@dhcp37-136 ~]# pvs -o +pe_start /dev/vdf PV VG Fmt Attr PSize PFree 1st PE /dev/vdf vg-test-brick2 lvm2 a-- 100.00g 1.25m 1.25m When a brick is created using RAID0 (on RHEL7) with 1 disk and 256KB stripe size below is the data alignment value. On RAID0: -------------------- -------------------- [root@dhcp37-68 ~]# pvs -o +pe_start /dev/vde PV VG Fmt Attr PSize PFree 1st PE /dev/vde RHS_vg4 lvm2 a-- 100.00g 5.00m 1.25m