Red Hat Bugzilla – Bug 770970
lvm2 man page and documentation for "normal" Allocation Policy needs to be improved
Last modified: 2013-01-08 02:11:42 EST
Description of problem:
Documentation describing lvm2 "normal" allocation policy is not very comprehensive and needs to be improved in order to allow the reader to be fully aware about how the extents of a logical volume are allocated.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is the only description available about how normal policy works in the man page:
"The default for a volume group is normal which applies common-sense rules such as not placing parallel stripes on the same physical volume"
In the Logical Volume Manager Administration guide the description is pretty the same.
A more comprehensive description about how extents are allocated throughout PVs possibly with details and examples.
The same applies to RHEL6 as well.
Yes, we can provide more-detailed documentation.
- How the set of 'available' extents is generated (command line, existing space)
- Outline of the process and how the --alloc policy affects it
- Rules for 'parallel' extents (mirror, stripes)
- Description of each policy
Not to cover specific implementation details (i.e. the bits that are not guaranteed and might change from release to release)
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Verified the new "ALLOCATION" section in the lvm man page.
When an operation needs to allocate Physical Extents for one or more Logical Volumes, the tools proceed as follows:
lvm2-2.02.88-10.el5 BUILT: Tue Aug 28 01:21:59 CDT 2012
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.