From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev: remove node only if major/minor matches
Date: Fri, 18 Feb 2005 19:13:01 +0000 [thread overview]
Message-ID: <20050218191301.GA22910@us.ibm.com> (raw)
In-Reply-To: <20050217031313.GA7282@vrfy.org>
On Thu, Feb 17, 2005 at 04:13:13AM +0100, Kay Sievers wrote:
> Hi Hannes,
> here we remove the device node only if the major/minor number matches
> the one in our database. Will this solve the possible issue with the multipath
> setup, where a device remove event may delete a node which belongs to a
> different path?
If device nodes are being overwritten, how does not removing an
overwritten /dev help?
Don't the multipath tools already require a separate sd /dev for proper usage
(i.e. path checker)?
It would be much better to never overwrite a correct /dev entry. Paths (i.e.
sd's) should really be named based on their sysfs or physical path, or
just the default name; the dm device should be named based on disk or
device specific attributes (scsi_id, volume_id, etc.). There is no good
way to know if dm is going to use an sd in a dm multipath.
If "%e" would always work, that might help.
-- Patrick Mansfield
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-02-18 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 3:13 udev: remove node only if major/minor matches Kay Sievers
2005-02-17 17:16 ` Greg KH
2005-02-18 18:59 ` Hannes Reinecke
2005-02-18 19:13 ` Patrick Mansfield [this message]
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=20050218191301.GA22910@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).