From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: inconsistent renaming of devices
Date: Fri, 06 Feb 2004 00:18:35 +0000 [thread overview]
Message-ID: <20040206001835.GA3753@vrfy.org> (raw)
In-Reply-To: <marc-linux-hotplug-107165372413670@msgid-missing>
On Thu, Feb 05, 2004 at 03:29:41PM +0530, Surekha.PC wrote:
>
>
> >What do you see happening in your system?
> >If you build with DEBUG=true USE_LOG=true what does the debug syslog
> show for these
> >devices?
>
> It seems the user<->kernel race still persists.
>
> During device addition randomly few device/partition entries are not
> getting created. If debug is enabled all devices are created. With debug
> turned off, only few of them are created. So in this case I am not able
> to capture debug for devices not getting created.
>
> Again device removal is also having the similar inconsistent behaviour.
> Irrespective of debug being on/off few stale device entries are retained
> under /udev.
>
> In this scenario I could see some debug messages as below.
>
> Looks like the sysfs entries for the device are removed long before udev
> lookup.
We don't need sysfs for device removal.
> ------------------------------------------------------------------------
> -----------------
> udev_hotplug: looking at '/block/sdc'
> udev_hotplug: looking at '/block/sde/sde2
> udev_hotplug: looking at '/block/sde/sde3
> get_dirs: sysfs_path='/sys'
> udev_hotplug: don't care about 'scsi_device' devices
> .....
> namedev_init_rules: reading '/etc/udev/udev.rules' as rules file
> .....
> udev_hotplug: looking at '/block/sdc/sdc3
> udev_hotplug: don't care about 'scsi_device' devices
> udev_remove_device: name is 'iscsib0t38l0sd3'
> ......
> udev_remove_device: '/class/scsi_device/40:0:38:1' not found in
> database, falling back on default name
Huh, what version of udev is this?
'scsi_device' is blacklisted.
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next prev parent reply other threads:[~2004-02-06 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 9:33 inconsistent renaming of devices Martin Lorenz
2003-12-17 18:13 ` Greg KH
2004-02-05 6:40 ` Surekha.PC
2004-02-05 8:56 ` Greg KH
2004-02-05 9:56 ` Olaf Hering
2004-02-05 10:11 ` Surekha.PC
2004-02-05 23:49 ` Greg KH
2004-02-05 23:51 ` Greg KH
2004-02-06 0:18 ` Kay Sievers [this message]
2004-02-06 6:34 ` Surekha.PC
2004-02-06 9:18 ` 'Kay Sievers'
2004-02-06 11:29 ` Surekha.PC
2004-02-08 14:13 ` Olaf Hering
2004-02-09 5:51 ` Ananth N Mavinakayanahalli
2004-02-09 6:31 ` Olaf Hering
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=20040206001835.GA3753@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 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.