Bug 457437 - RHEL 4.7 manual typo in lvextend of a striped volume
Summary: RHEL 4.7 manual typo in lvextend of a striped volume
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: Documentation
Version: 4.7
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: Content Services Development
URL:
Whiteboard:
Depends On: 349911
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-31 17:24 UTC by Steven J. Levine
Modified: 2009-06-12 20:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-12 20:39:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steven J. Levine 2008-07-31 17:24:28 UTC
+++ This bug was initially created as a clone of Bug #349911 +++

In the RHEL5 cluster LVM manual, on page 45 of the PDF version, when explaining
how to extend a striped LV when not enough space exists to extend using the same
stripe setup, it mentions to use -iL.  From what I can find, this is invalid -
you would instead use -i1. 

<context follows>
volume, but you can override those parameters. The following example extends the
existing
striped logical volume to use the remaining free space after the initial
lvextend command fails.
# lvextend vg/stripe1 -L 406G
   Using stripesize of last segment 64.00 KB
   Extending logical volume stripe1 to 406.00 GB
   Insufficient suitable allocatable extents for logical volume stripe1: 34480
more required
# lvextend -iL -l+100%FREE vg/stripe1

-- Additional comment from nstraz on 2007-12-13 12:45 EST --
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.

-- Additional comment from slevine on 2008-07-31 12:36 EST --
I have fixed the lvextend example so that it specifies the actual number 1
(indicating that the volume should be extended on to one stripe, which is
pragmatically not really a stripe...) instead of the typo-ed letter L. Good catch.

I have requested that the updated version of the document be pushed out to the
docs web page, with RT 26340.

Comment 1 Steven J. Levine 2009-06-12 20:39:17 UTC
With the release of RHEL 4.8, the LVM document is now correct.


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