Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 789630

Summary: dm_mod aka dm-mod.ko is loaded by default but i not use RAID or LVM
Product: Red Hat Enterprise Linux 6 Reporter: xset1980
Component: device-mapperAssignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1CC: agk, dwysocha, heinzm, jbrassow, mbroz, prajnoha, prockai, thornber, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-11 21:49:00 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 xset1980 2012-02-11 21:10:56 UTC
Description of problem:

dm_mod is loaded in SL6.1, but i no use RAID or LVM.
The script /etc/rc.d/rc.sysinit contain:

# Device mapper & related initialization
if ! __fgrep "device-mapper" /proc/devices >/dev/null 2>&1 ; then
       modprobe dm-mod >/dev/null 2>&1
fi

And, my /proc/devices contain 253 device mapper device, but, i no use RAID or LVM, so, is a kernel or device-mapper bug?


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

SL6.1, kernel 2.6.32-220.4.1.el6.i686

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:

The kernel module dm-mod.ko is loaded by default, but the system not use RAID or LVM


Expected results:

No load dm_mod


Additional info:

Comment 2 Milan Broz 2012-02-11 21:49:00 UTC
No it is not a bug.

Some kernel modules all loaded to ensure that storage stack always contains
this functionality - if you plug in disk with e.g. LUKS (encrypted flash) or
LVM it can be then handled properly. And several RHEL system scripts require
dm-ioctl
functionality (mkinitrd for kernel upgrade for example).

If you have some "hardened" or tuned installation, you can rmmod that later of
course but you can expect some warning later.

In /proc/devices is just registered device type, not a real mapped device (for
real mapped device see "dmsetup table" - it should be empty in your case.

Comment 3 Alasdair Kergon 2012-02-12 00:28:49 UTC
*** Bug 789639 has been marked as a duplicate of this bug. ***

Comment 4 Alasdair Kergon 2012-02-12 00:31:26 UTC
As Milan says, if you know for certain you won't need it later in the life of the system and it bothers you, just 'rmmod' the module at the end of initialisation.