From: Ian Kent <raven@themaw.net>
To: Joe Pruett <joey@clean.q7.com>
Cc: autofs@linux.kernel.org
Subject: Re: hung server again
Date: Wed, 19 Nov 2008 00:57:39 +0900 [thread overview]
Message-ID: <1227023859.3045.83.camel@zeus.themaw.net> (raw)
In-Reply-To: <alpine.LRH.2.00.0811180725001.21620@q7.q7.com>
On Tue, 2008-11-18 at 07:40 -0800, Joe Pruett wrote:
> a few months back i had a situation where a child of automount wouldn't
> exit properly and that would cause the parent to get locked up and all
> automount would stop working. if i could get onto the system, i could
> strace the child automounts and watch them exit and eventually i'd hit the
> one that was the cause and then everything would start working again.
> there have been a number of kernel updates since and it looked like things
> were working normally again. but i was wrong, our web server locked up
> last night from the same issue again. given the length of time between
> issues and the infeasibility of debugging this on a live server i want to
> ask about my setup and see if i should change things.
How about version of autofs and kernel?
>
> i use a two level automount hierarchy. /home entries are all designed to
> be bind mounts, like:
>
> joey :/disks/hyperion.0/home/joey
>
> and then /disks is a normal automount map:
>
> hyperion.0 hyperion:/disk/0
>
> repeat this for a few thousand /home entries, but only a handful of
> entries in /disks. i have done this to avoid thousands of nfs mounts on a
> busy server (like a mail server). in the past with udp it was bad enough,
> but now with tcp based nfs, each mount uses even more resources (sockets,
> tcp buffers, etc). but given this lockup bug, i am thinking of going to a
> straight single level /home setup.
>
> i did some testing with a single level /home and if i touch all entries in
> /home, i eventually ran into some resource limits. maybe there is some
> tuning i can do? i could go back to /home just being full of symlinks,
> but that has so many issues of it's own. i'm looking for feedback of other
> users that might have servers with a thousand or more active mounts and
> how that works for you. or some other good ideas of how people handle
> this kind of thing.
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2008-11-18 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 15:40 hung server again Joe Pruett
2008-11-18 15:57 ` Ian Kent [this message]
2008-11-18 16:39 ` Joe Pruett
2008-11-18 18:31 ` Joe Pruett
2008-11-18 19:51 ` Jeff Moyer
2008-11-18 20:08 ` Joe Pruett
2008-11-18 20:17 ` Jeff Moyer
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=1227023859.3045.83.camel@zeus.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=joey@clean.q7.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.