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 _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
