All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Marion <mmarion@qualcomm.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Seeing some 5.0.1 stop expiring mounts
Date: Fri, 27 Jul 2007 15:06:08 -0700	[thread overview]
Message-ID: <20070727220608.GD26192@cornholio.qualcomm.com> (raw)
In-Reply-To: <1185507080.3203.15.camel@raven.themaw.net>

On Fri, Jul 27, 2007 at 11:31:20AM +0800, Ian Kent wrote:

> Don't mean to be a pain but have you had time to check this?

Not a pain.. too much got in the way this week. I was able to test that
patch both against 5.0.1 with the
autofs-5.0.1-map-update-source-only.patch 
and against 5.0.2 and it's good.

Just to show, here's 5.0.2 without those 2 lines patched in2

vbr2-001:/usr/src/packages/SOURCES # ps auxw | grep automount
root      6812  0.7  0.0  28552  7180 ?        Ssl  13:59   0:00
automount
root      6935  0.0  0.0   2888   704 pts/1    S+   14:00   0:00 grep
automount
vbr2-001:/usr/src/packages/SOURCES # wc /proc/mounts; mount | wc ; kill
-HUP 6812; while [ 1 ]; do wc /proc/mounts ; mount | wc; sleep 5; done
6314 37884 730725 /proc/mounts
     12      72     441
6314 37884 730725 /proc/mounts
     12      72     441
6107 36642 706276 /proc/mounts
     12      72     441
5964 35784 689905 /proc/mounts
     12      72     441
5833 34998 674567 /proc/mounts
     12      72     441
5695 34170 658506 /proc/mounts
     12      72     441
5477 32862 633119 /proc/mounts
     12      72     441


and on down until all the auto.projects entries are gone... which takes
awhile.

The syslog shows them all being unmounted, unlike 5.0.1 it only shows
the "rmdir lmstat of <path> failed" messages for things that were
actually nfs mounted vs the entire auto.projects tree though.

-- 
Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com
Lisa: "As you know, we've been swimming. And we've developed a taste for it. We
agree that getting our own pool is the way to go. Now before you respond, you 
should know that your refusal will result in months and months of..."
Bart, Lisa: "CanwehaveapoolDad? CanwehaveapoolDad? CanwehaveapoolDad? 
CanwehaveapoolDad? CanwehaveapoolDad?"
Homer: "I understand. Let us celebrate our agreement with the adding of chocolate to milk." -- Simpsons

  reply	other threads:[~2007-07-27 22:06 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
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 [this message]
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=20070727220608.GD26192@cornholio.qualcomm.com \
    --to=mmarion@qualcomm.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.