Re: Issues with mkinitrd and path priority modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 28, 2008 at 02:55:15PM -0700, Pradipmaya Maharana wrote:
> Hi All,
> 
> I have created mpath_prio_custom, based on code from mpath_prio_alua.
> I specified the module in /etc/multipath.cong for getting priority of
> the luns.
> 
> prio_callout	"/sbin/mpath_prio_custom /dev/%n"
> 
> The module gets installed under /sbin with out any error, gives me
> correct priorities and runs fine; but while this module is installed
> if I do an mkinitrd, my module does not get included in the initrd
> image.  And due to this, when the kernel boots next time, it fails. As
> my module is mentioned in the multipath.conf, kernel tries to find
> this module under /sbin but cannot find it and hence it fails. I see
> other modules, mpath_prio_alua, mpath_prio_emc, etc. are part of the
> initrd image.
> 
> What must I do so that my module gets included as a part of initrd image.

Edit the 'mkinitrd' program to include this in. You didn't say what distro
you are using so it is hard to say what else you might need to modify.

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux