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.
Bug 1153312 - support non-power-of-2 VG physical extents
Summary: support non-power-of-2 VG physical extents
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: pre-dev-freeze
: 6.7
Assignee: Alasdair Kergon
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1142773 1153398 1164920
TreeView+ depends on / blocked
 
Reported: 2014-10-15 18:21 UTC by Mike Snitzer
Modified: 2017-02-07 13:53 UTC (History)
11 users (show)

Fixed In Version: lvm2-2.02.118-3.el6
Doc Type: Enhancement
Doc Text:
Clone Of: 1100514
Environment:
Last Closed: 2015-09-30 10:18:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mike Snitzer 2014-10-15 18:21:54 UTC
+++ This bug was initially created as a clone of Bug #1100514 +++

Description of problem:

lvm2 needs to support the creation of non-power-of-2 aligned logical volumes.

If a HW raid6 device is composed of 10 devices, with a chunk size of 64K, the overall raid stripe is 640K.  640K is _not_ a power of 2.  The pvcreate --dataalignment flag supports non-power-of-2 values so the PVs' data area is aligned relative to the underlying storage's alignment... but when these non-power-of-2 aligned PVs are added to a VG the Logical Volumes that are layered ontop cannot be properly aligned to the underlying PVs' alignment because the VG's physical extent cannot be configured to be a non-power-of-2.

The current workaround is to use a physical extent size that is compatible with the underlying PVs' non-power-of-2 alignment (e.g. use 64k if the raid stripe size is 640k).  But the lvcreate command doesn't know to align the LV relative to the underlying PVs' data alignment (as specified via pvcreate --dataalignment).  SO: the user needs to also use lvcreate -l <# extents> to specify the appropriate number of extents that would perfectly align the LV to the underlying PVs' data alignment.

--- Additional comment from Alasdair Kergon on 2014-10-14 13:20:17 EDT ---

https://lists.fedorahosted.org/pipermail/lvm2-commits/2014-October/002944.html

(Like I said, any further changes should go onto separate bugzillas for separate consideration.)

Comment 5 Alasdair Kergon 2015-09-30 10:18:43 UTC
Included in 6.7 automatically.


Note You need to log in before you can comment on or make changes to this bug.