autofs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

From: "Cyril B." <cbay@excellency.fr>
To: autofs@vger.kernel.org
Subject: automount subprocesses accumulate
Date: Thu, 10 Sep 2015 16:43:39 +0200	[thread overview]
Message-ID: <55F1971B.1050301@excellency.fr> (raw)

Hello,

I've been using autofs for a long time to mount NFS servers under /nfs, 
and recently started using it for mounting /home subdirectories as well 
(which point on /nfs/).

Since I've started automounting /home, I have automount subprocesses 
accumulating and never exiting:

root 1761264 0.0 0.0 205416 1478 ? Ssl 14:06 0:00 /usr/sbin/automount 
--pid-file /var/run/autofs.pid
root 1966587 0.0 0.0 209816 1564 ? S 14:45 0:00 \_ /usr/sbin/automount 
--pid-file /var/run/autofs.pid
root 2023507 0.0 0.0 209816 1652 ? S 15:00 0:00 \_ /usr/sbin/automount 
--pid-file /var/run/autofs.pid
root 2203212 0.0 0.0 215100 1900 ? S 15:45 0:00 \_ /usr/sbin/automount 
--pid-file /var/run/autofs.pid

My main automount was started at 14:06, and all subprocesses are stuck in a:

futex(0x56122035a5a0, FUTEX_WAIT_PRIVATE, 2, NULL

(same futex address for all of them).

There are typically a few new subprocesses each hour. I've already seen 
up to 20/25 subprocesses before I had to restart automount and kill them 
manually.

I have a lot of users on this server, so automount is serving many 
requests. Especially at round times (14:00, 14:15, 14:30, etc.), when 
cron starts many user processes. According to automount debug logs, up 
to 20 new home subdirectories can be mounted every second.

I'm using autofs 5.1.1 on Linux 4.1.4. My config:

/etc/auto.master:
--
/nfs program:/etc/auto.nfs
/home program:/etc/auto.home
--

/etc/auto.nfs is pretty standard, has been working fine for ages. It's 
basically returning:

-fstype=nfs4,noatime,nosuid,_netdev,soft,intr,timeo=1000 $1:/

/etc/auto.home:
--
#!/bin/sh

if [ ! -h /var/home/$1 ]
then
   exit 1
fi

echo -fstype=bind :$(readlink --no-newline /var/home/$1)
--

So for instance, /var/home/foo would be a symlink pointing to 
/nfs/serverX/foo.

autofs is compiled with --disable-mount-locking as recursive mounting 
wouldn't work otherwise.

Thanks!

-- 
Cyril B.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

next             reply	other threads:[~2015-09-10 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 14:43 Cyril B. [this message]
2015-09-11  5:34 ` automount subprocesses accumulate Ian Kent
2015-09-11 15:14   ` Cyril B.
2015-09-13 11:09     ` Ian Kent
2015-09-13 11:20       ` Cyril B.
2015-09-13 11:52         ` Ian Kent
2015-09-13 12:05           ` Cyril B.
2015-09-13 16:53             ` Cyril B.
2015-09-14  1:30             ` 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=55F1971B.1050301@excellency.fr \
    --to=cbay@excellency.fr \
    --cc=autofs@vger.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

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 read-only IMAP folder(s) and NNTP newsgroup(s).