From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 01 Oct 2004 09:57:28 +0000 Subject: Re: Hanging udev process on nfs-mounted /dev Message-Id: <1096624648.4295.85.camel@localhost.localdomain> List-Id: References: <415980BF.1020401@bio.ifi.lmu.de> In-Reply-To: <415980BF.1020401@bio.ifi.lmu.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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