unwanted kpartx partition delimiter persistance

unwanted kpartx partition delimiter persistance

[Ron Peterson]

Hi,

I have a strange problem w/ a new server.  Debian Lenny, kernel 2.6.27.26.

While getting our multipath setup going, we edited
/etc/udev/rules.d/z60_kpartx.rules to change the partition delimiter to
'quack'.

That's not the name we want in production, of course, so we changed it
to 'p'.  The problem is, on every reboot, the /dev/mapper (and
/dev/disk/...) names come up with the old delimiter - 'quack'.

If I run 'multipath -F', and 'multipath -v2', then the device names are
created as we'd expect them to.

We have grep'd for the string 'quack' everywhere it we can think of, and
it's nowhere to be found.  There is one kpartx config file in
/etc/udev/rules.d only.  What could cause the old name to persist like
this?

TIA

-Ron-

Re: unwanted kpartx partition delimiter persistance

[Mike Anderson]

Ron Peterson <rpeterso@mtholyoke.edu> wrote:
> Hi,
> 
> I have a strange problem w/ a new server.  Debian Lenny, kernel 2.6.27.26.
> 
> While getting our multipath setup going, we edited
> /etc/udev/rules.d/z60_kpartx.rules to change the partition delimiter to
> 'quack'.
> 
> That's not the name we want in production, of course, so we changed it
> to 'p'.  The problem is, on every reboot, the /dev/mapper (and
> /dev/disk/...) names come up with the old delimiter - 'quack'.
> 
> If I run 'multipath -F', and 'multipath -v2', then the device names are
> created as we'd expect them to.
> 
> We have grep'd for the string 'quack' everywhere it we can think of, and
> it's nowhere to be found.  There is one kpartx config file in
> /etc/udev/rules.d only.  What could cause the old name to persist like
> this?
> 

I do not have this distro available so my information may not be that
useful. but..

It sounds like there is a copy of the old rules in your initrd. 

Did you update your initrd post adding "quack" and if so did you run it
again after removing "quack"? 

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com

Re: unwanted kpartx partition delimiter persistance

[Ron Peterson]

2009-11-09_16:43:56-0500 Mike Anderson <andmike@linux.vnet.ibm.com>:
> Ron Peterson <rpeterso@mtholyoke.edu> wrote:

> > While getting our multipath setup going, we edited
> > /etc/udev/rules.d/z60_kpartx.rules to change the partition delimiter to
> > 'quack'.
> > 
> > That's not the name we want in production, of course, so we changed it
> > to 'p'.  The problem is, on every reboot, the /dev/mapper (and
> > /dev/disk/...) names come up with the old delimiter - 'quack'.

> It sounds like there is a copy of the old rules in your initrd. 
> 
> Did you update your initrd post adding "quack" and if so did you run it
> again after removing "quack"? 

Ah.  Yes, I compiled a new kernel.  I don't have time at the moment to
verify this, but that's a very good lead.  Thanks!

-Ron-

Re: unwanted kpartx partition delimiter persistance

[Ron Peterson]

2009-11-09_17:44:30-0500 Ron Peterson <rpeterso@mtholyoke.edu>:
> 2009-11-09_16:43:56-0500 Mike Anderson <andmike@linux.vnet.ibm.com>:
> > Ron Peterson <rpeterso@mtholyoke.edu> wrote:
> 
> > > While getting our multipath setup going, we edited
> > > /etc/udev/rules.d/z60_kpartx.rules to change the partition delimiter to
> > > 'quack'.
> > > 
> > > That's not the name we want in production, of course, so we changed it
> > > to 'p'.  The problem is, on every reboot, the /dev/mapper (and
> > > /dev/disk/...) names come up with the old delimiter - 'quack'.
> 
> > It sounds like there is a copy of the old rules in your initrd. 
> > 
> > Did you update your initrd post adding "quack" and if so did you run it
> > again after removing "quack"? 

That was it.  I just upgraded to 2.6.27.39, with udev configured to use
'p' as the partition delimiter, and that is now how it boots.  The hair
I have left is very grateful.  Thanks for your help!

-Ron-