Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
targetcli-2.0rc1.fb19-1.el7.noarch
kernel-3.7.0-0.30.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. create a mdadm raid0 based on 2 devices with the chunk size 4MB
#cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 vdc[1] vdb[0]
2088960 blocks super 1.2 4096k chunks
2. create the PV on the /dev/md0
#pvs -o+pe_start /dev/md0
PV VG Fmt Attr PSize PFree 1st PE
/dev/md0 vg lvm2 a-- 1.98g 1.91g 8.00m
3. create the vg based on the PV with PE size 8MB ( it's equal to the stripe width of the md0 )
#vgs -o+vg_extent_size
VG #PV #LV #SN Attr VSize VFree Ext
vg 1 1 0 wz--n- 1.98g 1.91g 8.00m
4. create a LV based on the vg then check the LV io_minimal_size and io_opt_size
#blockdev --getiomin --getioopt /dev/vg/lv01
4194304
8388608
5. create a block store based on the LV then export it via the loop device then check the exported device's io_minimal_size and io_opt_size.
#cat /sys/block/sdc/device/vendor
LIO-ORG
#blockdev --getiomin --getioopt /dev/sdc
512
4194304
Actual results:
#blockdev --getioopt /dev/sdc /dev/vg/lv01
4194304
8388608
#blockdev --getiomin /dev/sdc /dev/vg/lv01
512
4194304
Expected results:
the exported device should has the same io_minimal_size and io_opt_size as the LV's
Additional info:
Description of problem: Version-Release number of selected component (if applicable): targetcli-2.0rc1.fb19-1.el7.noarch kernel-3.7.0-0.30.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. create a mdadm raid0 based on 2 devices with the chunk size 4MB #cat /proc/mdstat Personalities : [raid0] md0 : active raid0 vdc[1] vdb[0] 2088960 blocks super 1.2 4096k chunks 2. create the PV on the /dev/md0 #pvs -o+pe_start /dev/md0 PV VG Fmt Attr PSize PFree 1st PE /dev/md0 vg lvm2 a-- 1.98g 1.91g 8.00m 3. create the vg based on the PV with PE size 8MB ( it's equal to the stripe width of the md0 ) #vgs -o+vg_extent_size VG #PV #LV #SN Attr VSize VFree Ext vg 1 1 0 wz--n- 1.98g 1.91g 8.00m 4. create a LV based on the vg then check the LV io_minimal_size and io_opt_size #blockdev --getiomin --getioopt /dev/vg/lv01 4194304 8388608 5. create a block store based on the LV then export it via the loop device then check the exported device's io_minimal_size and io_opt_size. #cat /sys/block/sdc/device/vendor LIO-ORG #blockdev --getiomin --getioopt /dev/sdc 512 4194304 Actual results: #blockdev --getioopt /dev/sdc /dev/vg/lv01 4194304 8388608 #blockdev --getiomin /dev/sdc /dev/vg/lv01 512 4194304 Expected results: the exported device should has the same io_minimal_size and io_opt_size as the LV's Additional info: