From: Ian Kent <raven@themaw.net>
To: harri@afaics.de
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-ext4@vger.kernel.org,
autofs@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [Bug 53951] race condition on mounting local disks with autofs
Date: Thu, 06 Feb 2014 08:18:49 +0800 [thread overview]
Message-ID: <1391645929.2608.17.camel@perseus.fritz.box> (raw)
In-Reply-To: <20140205174917.GH11667@thunk.org>
On Wed, 2014-02-05 at 12:49 -0500, Theodore Ts'o wrote:
> Original bug report, from https://bugzilla.kernel.org/show_bug.cgi?id=53951:
>
> Harald Dunkel 2013-02-16 15:55:40 UTC
>
> I am using autofs to mount a local disk to /misc/data6 on
> request. Problem: It seems that the first access silently fails, if
> the disk is not yet mounted.
Does it!
Or is it the mix of system calls that are made, some of which won't
trigger the mount and others that will. I know from experience that
find(1) does a fairly unusual mix of these calls.
Does it still happen if you append a "/" to /misc/data6.
Since there are a number of system calls that won't trigger mounts,
which is required to avoid mount storms, there needs to be some way to
selectively force mount triggering and appending a "/" to a path is the
way it's done (at least it should function that way).
Mind you the mix of calls won't matter if the automount is mounted
"nobrowse" since mount point directories that don't yet exist should
trigger a mount on any access.
The default installed autofs configuration sets this but if you wiped
out the configuration and didn't retain that setting then the automount
will be mounted "browse", the internal program default.
What are you using for that setting?
Ian
next prev parent reply other threads:[~2014-02-06 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 15:55 [Bug 53951] New: race condition on mounting local disks with autofs bugzilla-daemon
2014-02-05 17:03 ` [Bug 53951] " bugzilla-daemon
2014-02-05 17:49 ` Theodore Ts'o
2014-02-06 0:18 ` Ian Kent [this message]
2014-02-05 17:49 ` bugzilla-daemon
2014-02-06 0:19 ` bugzilla-daemon
2014-02-07 17:58 ` bugzilla-daemon
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=1391645929.2608.17.camel@perseus.fritz.box \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=harri@afaics.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 NNTP newsgroup(s).