archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <>
To: Andrew Morton <>
Cc: Kernel Mailing List <>,
	autofs mailing list <>,
	linux-fsdevel <>
Subject: [PATCH 2/5] autofs - update autofs.txt for strictexpire mount option
Date: Mon, 18 Mar 2019 09:00:30 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

A "strictexpire" mount option has been added to the autofs file

It is meant to be used in cases where a GUI continually accesses
or an application frquently scans an automount directory tree
causing an accumulation of otherwise unused mounts.

Signed-off-by: Ian Kent <>
 Documentation/filesystems/autofs.txt |   17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/Documentation/filesystems/autofs.txt b/Documentation/filesystems/autofs.txt
index 05da806b1e88..ac50b47f02bd 100644
--- a/Documentation/filesystems/autofs.txt
+++ b/Documentation/filesystems/autofs.txt
@@ -240,11 +240,18 @@ Normally the daemon only wants to remove entries which haven't been
 used for a while.  For this purpose autofs maintains a "`last_used`"
 time stamp on each directory or symlink.  For symlinks it genuinely
 does record the last time the symlink was "used" or followed to find
-out where it points to.  For directories the field is a slight
-misnomer.  It actually records the last time that autofs checked if
-the directory or one of its descendants was busy and found that it
-was.  This is just as useful and doesn't require updating the field so
+out where it points to.  For directories the field is used slightly
+differently.  The field is updated at mount time and during expire
+checks if it is found to be in use (ie. open file descriptor or
+process working directory) and during path walks. The update done
+during path walks prevents frequent expire and immediate mount of
+frequently accessed automounts. But in the case where a GUI continually
+access or an application frequently scans an autofs directory tree
+there can be an accumulation of mounts that aren't actually being
+used. To cater for this case the "`strictexpire`" autofs mount option
+can be used to avoid the "`last_used`" update on path walk thereby
+preventing this apparent inability to expire mounts that aren't
+really in use.
 The daemon is able to ask autofs if anything is due to be expired,
 using an `ioctl` as discussed later.  For a *direct* mount, autofs

  reply	other threads:[~2019-03-18  1:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  1:00 [PATCH 1/5] autofs - fix some word usage odities in autofs.txt Ian Kent
2019-03-18  1:00 ` Ian Kent [this message]
2019-03-18  1:00 ` [PATCH 3/5] autofs - update AUTOFS_EXP_LEAVES description Ian Kent
2019-03-18  1:00 ` [PATCH 4/5] autofs - update mount control expire desription with AUTOFS_EXP_FORCED Ian Kent
2019-03-18  1:00 ` [PATCH 5/5] autofs - add description of ignore pseudo mount option 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).