AutoFS development
 help / color / mirror / Atom feed
From: Steve Thompson <smt@vgersoft.com>
To: autofs@linux.kernel.org
Subject: Autofs hangs
Date: Mon, 14 Feb 2011 14:31:41 -0500 (EST)	[thread overview]
Message-ID: <alpine.LRH.0.9999.1102141422310.25310@firefly.vgersoft.com> (raw)

CentOS 5.5, 32- and 64-bit. Maps from LDAP. I upgraded recently (as part 
of a system-wide yum update) from autofs-5.0.1-0.rc2.143.el5_5.4 to 
autofs-5.0.1-0.rc2.143.el5_5.6, and ever since I have had a MASSIVE number 
of automount hangs (several per day across 170 systems). Nothing is 
logged, and the automount deamon is hung solid; only a SIGKILL and a 
restart can recover the daemon (and, if I wasn't already logged in, a 
power cycle is required - all accounts use automounted NFS home 
directories). Reading the Changelog, I see these changes:

- add mutex to serialize access to mount module handle in parse module
- dont check null cache on expire
- fix null cache race
- fix cache_init() on source re-read
- fix negative cache included map lookup

I don't know which of these to point the finger at, but I have also 
noticed many messages similar to:

automount<pid>]: update_negative_cache: key "<pid>" not found in map.

all of which are incorrect. Really need a fix for this asap - we're 
almost dead in the water.

-smt

             reply	other threads:[~2011-02-14 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 19:31 Steve Thompson [this message]
2011-02-15  3:32 ` Autofs hangs Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2011-03-09 19:11 autofs hangs Jaskaran Singh
2011-03-13  1:31 ` 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=alpine.LRH.0.9999.1102141422310.25310@firefly.vgersoft.com \
    --to=smt@vgersoft.com \
    --cc=autofs@linux.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