FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Device-mapper Development

 
 
LinkBack Thread Tools
 
Old 08-28-2008, 09:55 PM
"Pradipmaya Maharana"
 
Default Issues with mkinitrd and path priority modules

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.
Please help.

Thanks and Regards,
Pradipmaya.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 08-29-2008, 02:08 PM
Konrad Rzeszutek
 
Default Issues with mkinitrd and path priority modules

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@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 08-29-2008, 04:59 PM
"Pradipmaya Maharana"
 
Default Issues with mkinitrd and path priority modules

I am using RHEL 5.1.

Regards,
Pradipmaya.

On Fri, Aug 29, 2008 at 7:08 AM, Konrad Rzeszutek
<konrad@virtualiron.com> wrote:
> 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@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 
Old 08-29-2008, 09:26 PM
"Pradipmaya Maharana"
 
Default Issues with mkinitrd and path priority modules

Hi Konrad,

Thanks for your help.
I got what I need to do.

As I understand from the lines from mkinitrd below, I need to build 2
versions of my mpath_prio_custom; along with the normal one, I need to
build a static version with ".static" appended to the file name. The
mkinitrd looks for the "mpath_prio_*.static" files to copy.

<snip from mkinitrd>
# This includes all mpath_prio checkers in the image (~2.5M)
# Alternately we can only include those that are used by the
# current mpath config. This would require users to rebuild
# the initrd if migrating/adding controllers from different
# storage vendors
for M in /sbin/mpath_prio_*.static ; do
inst ${M} $MNTIMAGE/${M%%.static};
done
<snip>

Thanks and Regards,
Pradipmaya.


On Fri, Aug 29, 2008 at 7:08 AM, Konrad Rzeszutek
<konrad@virtualiron.com> wrote:
> 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@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

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

Thread Tools




All times are GMT. The time now is 04:09 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org