Bug 814764 - [RFE] Support 64-bit numbers of extents
[RFE] Support 64-bit numbers of extents
Status: NEW
Product: LVM and device-mapper
Classification: Community
Component: lvm2 (Show other bugs)
0-beta1
Unspecified Linux
medium Severity medium
: ---
: ---
Assigned To: LVM and device-mapper development team
cluster-qe@redhat.com
: FutureFeature, Reopened
: 815181 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-20 11:25 EDT by Alasdair Kergon
Modified: 2017-04-25 11:57 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 13:26:03 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: lvm‑technical‑solution?
rule-engine: lvm‑test‑coverage?


Attachments (Terms of Use)

  None (edit)
Description Alasdair Kergon 2012-04-20 11:25:55 EDT
Currently the number of extents in any LV is limited to 32 bits.  Large LVs use large extent sizes.

But with thin, mostly sparse, LVs, there comes a need for large LVs to have small extent sizes.

Consider compatibility, perhaps limiting this to thin LVs in the first instance.
Comment 1 Milan Broz 2012-04-23 02:10:14 EDT
*** Bug 815181 has been marked as a duplicate of this bug. ***
Comment 2 Tom Lavigne 2012-09-07 11:21:47 EDT
This request was evaluated by Red Hat Product Management for 
inclusion in the current release of Red Hat Enterprise Linux.
Since we are unable to provide this feature at this time,  
it has been proposed for the next release of 
Red Hat Enterprise Linux.
Comment 8 Heinz Mauelshagen 2016-07-27 13:26:03 EDT
We do map (small) thin chunks onto a thin pool DataLV with the current solution and keep track of their mapping on a thin MetaLV managed by the thin target, hence we don't require 64 bit extent numbers any more -> closing.

Feel free to reopen in case another requirement arises.
Comment 9 Zdenek Kabelac 2016-07-27 18:41:32 EDT
The reason why to support this is quite simple -

When you create 'small' extent size - you can't create large volume size -  so the comment 8 is not really relevant.

With 4MB extent you cannot create  4EB  thin volume - even though there is not other technical limitation -  the total size of LV is still expressed as 32bit * 32bit number.

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