Bug #37590
closed
I agree, a 1GiB size for extents doesn't make a lot of sense; that it makes reading LVM2 output easier to read when looking at extents is not really a good reason, and I'm not sure how it allows us to create larger LVs? (This limitations no longer applies for LVM2 format vs LVM1, no?)
Is the problem here that this is not explained in more detail? Or is there a different issue that needs to be solved?
Is there any news on this topic? Do we really plan to waste so much of available disk capacity on the LVM based setups?
There isn't anything different, we believe that the choice of 1GB for LVM extents made it an order of magnitude easier to calculate space available and the possible waste isn't significant enough to change back.
It becomes more of a problem on very small OSDs, but we aren't optimizing for that use case, so I would recommend pre-creating the LVs if using tiny OSDs is what is needed.
- Status changed from New to Fix Under Review
- Pull request ID set to 34740
- Status changed from Fix Under Review to Resolved
Also available in: Atom
PDF