AutoFS development
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Steve Thompson <smt@vgersoft.com>
Cc: autofs@linux.kernel.org
Subject: Re: Autofs hangs
Date: Tue, 15 Feb 2011 11:32:05 +0800	[thread overview]
Message-ID: <1297740725.13007.11.camel@perseus> (raw)
In-Reply-To: <alpine.LRH.0.9999.1102141422310.25310@firefly.vgersoft.com>

On Mon, 2011-02-14 at 14:31 -0500, Steve Thompson wrote:
> 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.

I can't see any obvious problems 
Can you get a gdb backtrace of a couple of the hangs and post them?
In particular I need the output of "thr a a bt".
Ian

  reply	other threads:[~2011-02-15  3:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 19:31 Autofs hangs Steve Thompson
2011-02-15  3:32 ` Ian Kent [this message]
  -- 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=1297740725.13007.11.camel@perseus \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=smt@vgersoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox