RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 613506 - Typo of displays (dispays) in LVM administration guide
Summary: Typo of displays (dispays) in LVM administration guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Logical_Volume_Manager
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On: 588934
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-12 04:12 UTC by Michael Hideo
Modified: 2010-11-11 15:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 588934
Environment:
Last Closed: 2010-11-11 15:35:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Hideo 2010-07-12 04:12:49 UTC
+++ This bug was initially created as a clone of Bug #588934 +++

Description of problem:

On both the Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 guide ( http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.5/html/Logical_Volume_Manager_Administration/mirvol_create_ex.html )

The text:

The output of this command dispays PE ranges in the same format that the lvcreate and lvresize commands take as input. 

Should be 

The output of this command displays PE ranges in the same format that the lvcreate and lvresize commands take as input. 

Version-Release number of selected component (if applicable):

Public website as of Tue May  4 16:47:49 EDT 2010

How reproducible:

Every page refresh.

Additional info:

Also visible in the el6 beta guide.

Comment 1 Steven J. Levine 2010-07-13 20:13:11 UTC
Thanks for catching this. I've fixed the typo in my working draft copy and this will be reflected in the final 6.0 version of the document. I also fixed the typo in the 5.5 draft and checked it in, so when that splits to 5.6 (or we reissue an update of 5.5) the typo will be fixed there as well.

Comment 5 Steven J. Levine 2010-09-20 22:21:05 UTC
The fixes were in my working draft, but I had not built the updated manual on the review server. I have now re-built the document on the review server so that it reflects the 6.0 working draft and the fix is here:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/mirvol_create_ex.html

Comment 7 releng-rhel@redhat.com 2010-11-11 15:35:12 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. 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.