Bug 297591

Summary: /etc/udev/rules.d/64-device-mapper.rules
Product: [Fedora] Fedora Reporter: Harald Hoyer <harald>
Component: device-mapper-obsoleteAssignee: Alasdair Kergon <agk>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: agk, dwysocha, mbroz, prockai
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-11 15:58:32 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:

Description Harald Hoyer 2007-09-20 09:12:52 UTC
Please provide the rule from /etc/udev/rules.d/64-device-mapper.rules:
KERNEL=="device-mapper",        NAME="mapper/control"

Comment 1 Alasdair Kergon 2007-09-20 12:04:27 UTC
Please explain further:

The /dev/mapper directory is not yet managed by udev, and can't be until the
lvm2/dm/udev integration work (that Kay is working on) is complete.

Comment 2 Harald Hoyer 2007-09-20 12:15:00 UTC
/dev/mapper/control is controlled by udev, IIRC. But if integration work is
already on the way, I will close this bug and leave the rule in udev.

Comment 3 Alasdair Kergon 2007-09-20 12:26:07 UTC
It's also controlled by libdevmapper in the sense that if it doesn't exist or
any of its properties are incorrect libdevmapper will (re)create it.

When the upstream integration work is complete, libdevmapper will no longer
change any /dev entries.