Red Hat Bugzilla – Bug 143024
pvmove does not autoload dm_mirror module
Last modified: 2014-03-16 22:51:13 EDT
When trying to use pvmove on fully updated RHEL4 Beta2 I've got this
error message (lvm2-2.00.25-1.01):
Required device-mapper target(s) not detected in your kernel
This could be avoided by loading module dm_mirror by hand.
To fix: pvmove should autoload dm_mirror automagically
Initscripts are supposed to load all dm modules if LVM is in use -
can you work out why they haven't? Are any device-mapper modules
Is / on lvm or not and does that make a difference?
Autoloading will be dealt with upstream sometime, but needs interface
The system is fresh RHEL4b2. LVM is auto mounted datastore (originally
LVM1) to /home (so no / on LVM - I'm using RAID1 for root FS). No dm*
modules are loaded when system starts and the LVM is started and
mounted when system boots. I'm using LABEL in fstab and I run
vgconvert to convert LVM1 to LVM2:
I have device-mapper in /proc/devices.
I see that rc.sysinit is trying to load dm-mod, but I have dm_mod in
output of lsmod and dm-mod.ko on the disc. Strange :)
Well. dm_mod is autoloaded when system boots. But not dm_mirror which
is required by pvmove. Sorry for confusion.
So it seems that initscripts should be fixed or so.
> Initscripts are supposed to load all dm modules if LVM is in use
That's the first I've heard of it. Why isn't it loaded on demand?
Closing this bug, due to response of the initial question.
Realistically, without any way to know what dm modules are needed, there's no
way to autoload.
Note that later releases, dm-mirror may be loaded before starting dmraid.