From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hanging udev process on nfs-mounted /dev
Date: Fri, 01 Oct 2004 06:25:20 +0000 [thread overview]
Message-ID: <415CF850.1050400@bio.ifi.lmu.de> (raw)
In-Reply-To: <415980BF.1020401@bio.ifi.lmu.de>
Kay Sievers wrote
> It would be nice to know, if there is posssibly one process spinning at
> this time, which blocks all the other processes? Or if there is a "real"
> deadlock, where all processes are blocking in the lock call.
As far as I remember, when the udev process was running with 90% cpu time,
it was the only udev process (pgrep udev).
> You may increase the alarm()-timout to have more than 20 seconds to
> investigate this :)
I will try, but the hosts where the problem occured most frequently are
desktop clients of research asisstants. So it is not that easy to debug
it without stopping the users from working :-)
> Yeah, it does not sound very sane to do concurrent writing to the same
> file over nfs without proper locking. A local tmpfs-based /dev seems
> more appropriate for that. It should be faster anyway and there is no
> reason to store the /dev anywhere while using udev.
With debugging and logging enabled now (needed for your patch to compile),
I get lots of messages from udev broadcasted to every shell, which is
quite annoying for the users, because they get all their xterms filled:
Oct 1 05:46:50 noether udevinfo[336]: rec_read bad magic 0xd9fee666 at offsety12
And this about 15 times, every time the card reader reconnects. On the
hosts where I already replaces /dev/ with a tmpfs, those messages do
not appear at all. Apart from /dev-over-nfs vs. /dev-over-tmpfs there
are no differences between these hosts. So it seems that the nfs causes
some other problems, that tmpfs is not suffering from. I would like
to switch all hosts to tmpfs immediately, but I'm afraid I won't get
any deadlocks anymore so that we cannot do useful debugging :-)
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-10-01 6:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 15:18 Hanging udev process on nfs-mounted /dev Frank Steiner
2004-09-29 17:18 ` Greg KH
2004-09-29 23:39 ` Kay Sievers
2004-09-30 2:11 ` Kay Sievers
2004-09-30 6:18 ` Frank Steiner
2004-09-30 6:21 ` Frank Steiner
2004-09-30 14:07 ` Kay Sievers
2004-10-01 6:25 ` Frank Steiner [this message]
2004-10-01 7:36 ` Kay Sievers
2004-10-01 7:38 ` Frank Steiner
2004-10-01 7:55 ` Frank Steiner
2004-10-01 8:08 ` Kay Sievers
2004-10-01 9:43 ` Frank Steiner
2004-10-01 9:57 ` Kay Sievers
2004-10-01 10:43 ` Kay Sievers
2004-10-01 22:18 ` Kay Sievers
2004-10-03 21:10 ` Frank Steiner
2004-10-03 23:07 ` Kay Sievers
2004-10-04 6:15 ` Frank Steiner
2004-10-04 14:19 ` Kay Sievers
2004-10-04 14:53 ` Frank Steiner
2004-10-05 15:37 ` Kay Sievers
2004-10-06 6:06 ` Frank Steiner
2004-10-06 12:00 ` Kay Sievers
2004-10-06 12:29 ` Frank Steiner
2004-10-08 5:59 ` Frank Steiner
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=415CF850.1050400@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--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).