autofs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Fitch <danielfitch@gmail.com>
To: autofs@vger.kernel.org
Subject: Autofs Question
Date: Thu, 17 Sep 2015 10:14:43 -0500	[thread overview]
Message-ID: <CAM2qnR73c7j5yFa+b2AA7zArFH9uODYGx9egW_ijthdisXRLQw@mail.gmail.com> (raw)

I was wondering if anyone could try to point me in the right direction
with this error that happens when reloading autofs.

We have thousands of users and we populate the /etc/auto.master file
with those users automounts that are currently logged into this
server.

/-   /path_to/automounts/user1/auto.user1_mounts --timeout=600
/-   /path_to/automounts/user2/auto.user2_mounts --timeout=600

Here is the typical scenario.
User logs in and  /etc/auto.master is populated with their automounts.
/etc/init.d/autofs reload is run and output to /var/log/syslog
contains the following message.

Sep 15 13:23:11 server automount: do_umount_autofs_direct: couldn't
get ioctl fd for direct mount
/path_to_a_mount_within_users_automount_file.

The " couldn't get ioctl fd for direct mount" message will repeat on
every reload.

The automaster files are in the following format.

/path_to_mount -rw,fstype=fuse,allow_other,port=PORT#
:sshfs\#remote_user@IP\:/remote_path

These are fuse mounts that are possibly within another datacenter.

Version

5.1.1

Compile options:

  LIBXML2_WORKAROUND

Ubuntu 14.04

Let me know if I can add any details and I will.

Thank you,

Dan
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

             reply	other threads:[~2015-09-17 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 15:14 Dan Fitch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14 16:23 Autofs question Robin Rosenberg

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=CAM2qnR73c7j5yFa+b2AA7zArFH9uODYGx9egW_ijthdisXRLQw@mail.gmail.com \
    --to=danielfitch@gmail.com \
    --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
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 read-only IMAP folder(s) and NNTP newsgroup(s).