Bug 517897
Summary: | Clarify documentation on partition creation and deletions for multipath and virtual machines | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Steven J. Levine <slevine> | |
Component: | doc-DM-Multipath_Guide | Assignee: | Steven J. Levine <slevine> | |
Status: | CLOSED WONTFIX | QA Contact: | ecs-bugs | |
Severity: | low | Docs Contact: | ||
Priority: | low | |||
Version: | 5.5 | CC: | iannis, slevine | |
Target Milestone: | rc | Keywords: | Documentation | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 466970 | |||
: | 966208 (view as bug list) | Environment: | ||
Last Closed: | 2013-05-22 19:17:07 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 466970 | |||
Bug Blocks: |
Comment 3
RHEL Program Management
2010-08-09 18:15:08 UTC
Ben Marzinski has verified that points 3 and 4 are correct, but that for point 3 you can just run # dmset info Leaving off the -c give you pretty formatting. However, as noted above, both points 3 and 4 are at a more detailed, internals level than the surrounding documentation in the DM-Multipath manual. Point 4 in particular doesn't seem to belong in the Dm-Multipath manual at all. This bug requires further exploration and research on my part, now that I at least have that info from Ben. This won't be done for RHEL 5.7 for certain. I'm moving this to RHEL 5.8 fornow although I think that if we do ultimately provide these detailed procedures it will be for RHEL 6. Moving the 5.9. I'm still not sure this is a priority to document, but I don't want to lose this request. Status unchanged. Moving to 5.10. I've cloned this bug for RHEL 6 and I'm closing this version. It's not clear whether we'll have the resources to research and address this, but if we do it will be moving forward with RHEL 6 as it's late in the RHEL 5 cycle. |