Bug 249004 - User interface to obtain usable dm devices (P2*)
Summary: User interface to obtain usable dm devices (P2*)
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: device-mapper   
(Show other bugs)
Version: 4.5
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Milan Broz
QA Contact: Corey Marthaler
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-20 09:44 UTC by Milan Broz
Modified: 2013-03-01 04:05 UTC (History)
13 users (show)

Fixed In Version: RHBA-2007-0749
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-15 15:58:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0749 normal SHIPPED_LIVE device-mapper bug fix and enhancement update 2007-11-14 17:04:55 UTC

Description Milan Broz 2007-07-20 09:44:24 UTC
+++ This bug was initially created as a clone of Bug #168533 +++
RHEL 4.6 clone, covering tree-based and dependency fields in dm

-- Additional comment from tao@redhat.com on 2005-09-16 17:32 EST --
From User-Agent: XML-RPC

dm devices can be stacked on other dm devices.

So some of dm devices are valid for mount, fsck, etc.,

while the others are not valid for such use.

Using libdevmapper, it's possible to obtain information about

dependencies between dm devices.

It can be extended to provide user-space tools to obtain

device listing valid for their use.


-- Additional comment from agk@redhat.com on 2007-03-30 14:14 EST --
Let's get the final piece of this cleaned up and included in 5.1 dmsetup.

Comment 6 errata-xmlrpc 2007-11-15 15:58:06 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.