From: Ian Kent <raven@themaw.net>
To: Mike Marion <mmarion@qualcomm.com>
Cc: autofs@linux.kernel.org
Subject: Re: Seeing some 5.0.1 stop expiring mounts
Date: Wed, 18 Jul 2007 14:42:30 +0800 [thread overview]
Message-ID: <1184740950.4178.45.camel@raven.themaw.net> (raw)
In-Reply-To: <20070717200433.GB14624@cornholio.qualcomm.com>
On Tue, 2007-07-17 at 13:04 -0700, Mike Marion wrote:
> On Tue, Jul 17, 2007 at 12:54:31PM -0700, Mike Marion wrote:
>
> > Wondering if anyone else has seen and/or has any idea what might be the
> > cause.
>
> Hmm.. might've found the cause at least.. common thread appears to be
> OOM situation hit on hosts in this state. Yes, our users do this a
> LOT.. it's a big pain, we're trying to find a balance between enforcing
> limits without killing batch jobs incorrectly.
>
> Luckily autofs5 seems to be the first autofs IME that you can kill -9
> then start a new one and have it take over the mounts properly.
Yep, it's seems to work well so far.
If you configure with --enable-ignore-busy (and for good measure
--disable-mount-locking) then you should be able to achieve the same
result with "service autofs restart", no kill needed at all.
Ian
next prev parent reply other threads:[~2007-07-18 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 19:54 Seeing some 5.0.1 stop expiring mounts Mike Marion
2007-07-17 20:04 ` Mike Marion
2007-07-18 6:42 ` Ian Kent [this message]
2007-07-18 6:46 ` Ian Kent
2007-07-18 21:39 ` Mike Marion
2007-07-19 10:08 ` Ian Kent
2007-07-19 12:03 ` Ian Kent
2007-07-19 12:12 ` Ian Kent
2007-07-19 23:40 ` Mike Marion
2007-07-27 3:31 ` Ian Kent
2007-07-27 22:06 ` Mike Marion
2007-07-28 6:51 ` Ian Kent
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=1184740950.4178.45.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=mmarion@qualcomm.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.