From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: udev hangs under high loads
Date: Sat, 23 Oct 2004 05:41:19 +0000 [thread overview]
Message-ID: <20041023054119.GA11915@kroah.com> (raw)
One of my coworkers (hi Nish) is trying to get 10000 disk support tested
and working properly with linux and ran into a nasty udev issue
yesterday. It seems that under a very high load, with a whole bunch of
hotplug events happening (for when the disks get added to the system),
udev hangs.
It hangs in the "grabbing the database lock" portion of the code (don't
have actual logs of where it hangs, will try to get that next week.)
But the interesting thing is we almost handle everything properly.
udev creates the node, tries to write to the database. Then the timer
expires and we report this. After the timer expires, udev is done for.
It just sits and spins, doing a nanosleep constantly. Have 500 of those
instances all running at once, all at a nice level of -10 is a sure way
to bring a box (even a relatively big one) down hard.
So, while I'll agree finding the root tdb locking bug is a good idea, I
wanted to point out that perhaps we should just exit udev if our timeout
expires, instead of still waiting around. Or do you have a better
solution?
Try testing this out on your own using the scsi_debug module and adding
a few hundred disks. It also helps if you have scsi generic support
enabled, as that creates 2 udev events for every disk created.
thanks,
greg k-h
-------------------------------------------------------
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 reply other threads:[~2004-10-23 5:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 5:41 Greg KH [this message]
2004-10-23 6:31 ` udev hangs under high loads Kay Sievers
2004-10-24 5:08 ` Kay Sievers
2004-10-24 5:53 ` Olaf Hering
2004-10-24 15:53 ` Kay Sievers
2004-10-24 15:57 ` Olaf Hering
2004-10-24 19:27 ` Kevin P. Fleming
2004-10-24 19:46 ` Kay Sievers
2004-10-24 19:51 ` Marco d'Itri
2004-10-24 19:56 ` Kay Sievers
2004-10-25 2:51 ` Kay Sievers
2004-10-25 7:01 ` Greg KH
2004-10-25 17:07 ` Kay Sievers
2004-10-25 17:12 ` Kevin P. Fleming
2004-10-25 17:27 ` Nishanth Aravamudan
2004-10-25 17:53 ` Kay Sievers
2004-10-25 20:55 ` Nishanth Aravamudan
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=20041023054119.GA11915@kroah.com \
--to=greg@kroah.com \
--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).