All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 19 Jul 2007 18:08:50 +0800	[thread overview]
Message-ID: <1184839730.3258.47.camel@raven.themaw.net> (raw)
In-Reply-To: <20070718213945.GA7455@cornholio.qualcomm.com>

On Wed, 2007-07-18 at 14:39 -0700, Mike Marion wrote:
> On Wed, Jul 18, 2007 at 02:46:07PM +0800, Ian Kent wrote:
> 
> > Might be worth considering going to 5.0.2, especially since you have a
> > busy site, as a nasty deadlock in the alarm handler has been fixed. 
> 
> Unfortunately, we can't.  I've since found out (through trial and error)
> that the patch:
> > > autofs-5.0.1-map-update-source-only.patch

Oops!

> 
> is completely broken for us, and it appears to be part of the 5.0.2
> codebase now.
> 
> Our main setup for auotofs5 clients now is pure ldap.. auto_master is in
> ldap, nsswitch.conf has
> automount: ldap
> everything is in ldap.  We remove all /etc/auto.* files too.
> 
> With the above patch applied to 5.0.1 (or using 5.0.2) as soon as the
> daemon gets a HUP signal, it flushes out all the auto.projects (our main
> map) entries from /proc/mounts and they're gone forever.
> 
> When first started, and until the daemon gets a HUP, it works fine.  Our
> /proc/mounts has 6200+ entries (we have a crapload of paths) and
> they'll mount great.  Entries look as expected, e.g.:
> auto.projects /prj/qct/gv autofs rw,fd=6,pgrp=2571,timeout=600,minproto=5,maxproto=5,direct 0 0
> then if you mount it, it adds in:
> ronald:/vol/eng_ice_0014/qct_gv /prj/qct/gv nfs rw,v3,rsize=32768,wsize=32768,acregmin=1,acregmax=5,acdirmin=1,acdirmax=5,hard,lock,proto=tcp,addr=ronald 0 0
> 
> After the HUP, the thing flushes, then logs a ton of rm_dir errors..
> like so:
> 
> Start of daemon:
> automount[2571]: mounted direct mount on /prj/qct/gv with timeout 600, freq 150 seconds
> 
> Flush after HUP:
> automount[2572]: umounted direct mount /prj/qct/gv
> 
> After all umounts.. these errors show for every path:
> automount[2549]: rmdir_path: lstat of /prj/qct/gv failed.
> 
> I did a test with 5.0.1 with all patchs sans the
> autofs-5.0.1-map-update-source-only.patch and it's fine... I can HUP
> left and right, do kill -USR1 to flush, etc.  Works right.  But rebuild again
> with that patch and first HUP breaks all our auto.projects paths.  Weird
> thing is the /net and /usr2 (indirect home dirs) stay working.  Those
> entries look like:
> $ egrep 'auto.home|/net' /proc/mounts | grep -v auto.projects
> -hosts /net autofs rw,fd=9,pgrp=13948,timeout=600,minproto=5,maxproto=5,indirect 0 0
> auto.home /usr2 autofs rw,fd=14,pgrp=13948,timeout=600,minproto=5,maxproto=5,indirect 0 0

So it sounds like the direct mounts are unhappy with this or possibly
the LDAP module.

I'll try to duplicate the problem.

Ian

  reply	other threads:[~2007-07-19 10:08 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
2007-07-18  6:46 ` Ian Kent
2007-07-18 21:39   ` Mike Marion
2007-07-19 10:08     ` Ian Kent [this message]
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=1184839730.3258.47.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.