All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: unwanted kpartx partition delimiter persistance
Date: Mon, 9 Nov 2009 13:43:56 -0800	[thread overview]
Message-ID: <20091109214356.GA8671@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091109211403.GH30590@mtholyoke.edu>

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

  reply	other threads:[~2009-11-09 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 21:14 unwanted kpartx partition delimiter persistance Ron Peterson
2009-11-09 21:43 ` Mike Anderson [this message]
2009-11-09 22:44   ` Ron Peterson
2009-11-10 13:44     ` Ron Peterson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091109214356.GA8671@linux.vnet.ibm.com \
    --to=andmike@linux.vnet.ibm.com \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.