Bug 166374 - [RHEL4] physicalextentsize 4KB is supported (lvm2 - vgcreate manpage)
Summary: [RHEL4] physicalextentsize 4KB is supported (lvm2 - vgcreate manpage)
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Alasdair Kergon
QA Contact: Brian Brock
: 182570 (view as bug list)
Depends On:
Blocks: 181409
TreeView+ depends on / blocked
Reported: 2005-08-19 20:56 UTC by Issue Tracker
Modified: 2018-10-19 19:04 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2006-08-10 21:45:06 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0504 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2006-08-10 04:00:00 UTC

Comment 5 David Milburn 2005-08-19 21:02:35 UTC
Manpage for vgcreate needs to specify the correct range for lvm2 physicalextentsize.

Comment 7 Alasdair Kergon 2005-08-30 13:07:55 UTC
"vgcreate in lvm2 allows 1 KB for minimum value in source code. It mentions
only for LVM1. should mention LVM2 also, since RHEL4 is using LVM2."

Comment 11 David Milburn 2005-10-21 21:44:14 UTC
The manpage for vgcreate delivered in lvm2-2.01.08-1.0.RHEL4 doesn't state the
correct physicalextentsize for LVM2.

-s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
      Sets  the physical extent size on physical volumes of this vol-
      ume group.  A size suffix (k for kilobytes up  to  t  for  ter-
      abytes)  is  optional, megabytes is the default if no suffix is
      present.  Values can be from 8 KB to 16 GB in powers of 2. 

The 8KB to 16GB range is specific to LVM1, it should state the correct limits
for LVM2 which would be 1KB to MAX.

Comment 15 Alasdair Kergon 2006-03-15 15:10:18 UTC
*** Bug 182570 has been marked as a duplicate of this bug. ***

Comment 16 Alasdair Kergon 2006-04-06 21:09:25 UTC
Committed upstream.

Comment 22 Red Hat Bugzilla 2006-08-10 21:45:22 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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