From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hanging udev process on nfs-mounted /dev
Date: Fri, 01 Oct 2004 09:57:28 +0000 [thread overview]
Message-ID: <1096624648.4295.85.camel@localhost.localdomain> (raw)
In-Reply-To: <415980BF.1020401@bio.ifi.lmu.de>
On Fri, 2004-10-01 at 09:55 +0200, Frank Steiner wrote:
> Kay Sievers wrote
>
> > This may be the process that blocks all the other ones. If you can find
> > one of these beasts, please attach gdb to the running process and look
> > if we find something in the backtrace. Here is a sample from my
> > "lock the whole file"-test application:
>
>
> Arrrgggh damn! I wish I had waited a bit longer with killing the process
> so that I had read this mail before and could have tried the gdb :-((
> But since it was the professors (my boss :-)) client, he wanted to have
> it back working quickly.
Hey, it already consumed 17 minutes of the CPU. I think he has a better
job for that CPU than a spinning udev :)
> >>Oct 1 05:46:50 noether udevinfo[336]: rec_read bad magic 0xd9fee666 at offsety12
> >
> >
> > Oops, that is from the tdb-code and indicates a corrupt database, which
> > is likely the reason for all the bad behavior. You may try to
> > "rm /dev/.udev.tdb" and look if these messages are going away. The next
> > udev run will create a new one.
>
> Hmm, this sounds like the problem is NFS without locking. Maybe two
> processes indeed write concurrently to the database, thus corrupting it.
> That would also explain why I don't see any of these messages on the
> tmpfs hosts.
This is probably what happens here, yes.
> > Does "udevinfo -d" (database dump) print anything?
>
> Not very much, just 4 entries:
This database if definitely corrupt.
> > The /dev is stored on nfs and not cleaned and recreated with udevstart
> > before mounting, right? So the database may be corrupt since a long
> > time?
>
> boot.udev is run on boot, so it recreates the database on every start,
> and thus, it looks like it gets corrupted again on almost every boot.
Weird! Please double check that this script is really running. There is
nothing in the boot.msg file, but I don't know if there should be some.
Thanks,
Kay
-------------------------------------------------------
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 9:57 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
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 [this message]
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=1096624648.4295.85.camel@localhost.localdomain \
--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 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).