Bug 749932 - Document new --nosync option of lvextend in LVM manual for RHEL 6.3
Summary: Document new --nosync option of lvextend in LVM manual for RHEL 6.3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Logical_Volume_Manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-28 22:09 UTC by Steven J. Levine
Modified: 2012-06-21 20:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 742311
Environment:
Last Closed: 2012-06-21 20:57:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Steven J. Levine 2011-10-28 22:09:29 UTC
This features will be going into RHEL 6.3, as per BZ#743640, so the documentation that is being put into the 5.8 version should be added to the RHEL 6 document as well.


+++ This bug was initially created as a clone of Bug #742311 +++

As per BZ#537369, there are plans to add a new option to lvextend in RHEL 5.8. If this gets finished and approved, I will need to document it. This BZ is a placeholder for this documentation.

--- Additional comment from slevine on 2011-10-28 13:17:41 EDT ---

I have written an entire new section of the LVM manual to document this feature and I have sent it to Jonathan Brassow for his review.

Comment 1 Steven J. Levine 2012-02-02 22:47:16 UTC
I have added the new information about lvextend --nosync that I wrote for 5.8 to the 6.3 draft. When I build the LVM document for 6.3 to send for review I will be sure this section gets looked at again.

Comment 2 Steven J. Levine 2012-03-07 18:39:29 UTC
I have sent the new section to jbrassow for a lookover, although it's identical to 5.8 so I anticipate no issues. Famous last words.

Comment 3 Steven J. Levine 2012-03-07 23:09:08 UTC
From Jon:

looks good steven, thanks.

 brassow


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