linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 30 Sep 2004 06:18:14 +0000	[thread overview]
Message-ID: <415BA526.8010905@bio.ifi.lmu.de> (raw)
In-Reply-To: <415980BF.1020401@bio.ifi.lmu.de>

Kay Sievers wrote

>>Seems we have two different problems here, one that sounds like a loop
>>consuming all the CPU and onother one, like the trace, which looks like
>>a F_SETLKW deadlock.
>>The traces are indicating a deadlock, where processes are simply waiting
>>for each other for a write-lock on the udev.tdb to be released.

That would match my observation that there seemed to be 2-3 udev processes
started almost at the same time. Since I recorded all the udev traces
with the ppid in the log name, I could see that there were always three
processes started close together (the log files having the same timestamp
and the ppids not differing much, like pids 29465, 29470 and 29473), so
they might deadlock.

However, also note that these problems so far occured only on hosts
having /dev/ mounted via NFS. Maybe the slow NFS traffic (in comparison
to the local hard disk) is well-suited for triggering the deadlock.

> Here is a patch that implements a timeout for the dead udev process. After
> 20 seconds the lock system call is interrupted and the error debug from tdb
> is logged to the syslog. I needed to port the sleep() calls, cause they
> are not compatible with alarm().

Thanks for the patch, I will apply it and try to reproduce the situations!
If I get a log, I will send it here.

A general question: Someone on the NFS mailing list proposed to remove
the NFS mount for dev and replace it by some tmpfs mounted on /dev.
SuSE is not really prepared for it, so udevstart misses a lot of devices
like /dev/stderr etc., but I could hack this myself easily.
Is it safe to assume that one should have less problems with a tmpfs
dev compared to a NFS mount?

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

  parent reply	other threads:[~2004-09-30  6:18 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 [this message]
2004-09-30  6:21 ` Frank Steiner
2004-09-30 14:07 ` Kay Sievers
2004-10-01  6:25 ` Frank Steiner
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=415BA526.8010905@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).