From: Ross Lagerwall <rosslagerwall@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Mount propagation issue
Date: Tue, 30 Sep 2014 18:46:55 +0100 [thread overview]
Message-ID: <20140930174655.GB10601@hobo.lan> (raw)
In-Reply-To: <87iok657jc.fsf@x220.int.ebiederm.org>
On Mon, Sep 29, 2014 at 04:30:31PM -0700, Eric W. Biederman wrote:
> Ross Lagerwall <rosslagerwall@gmail.com> writes:
> > I hope someone has an idea of what's going on or how to debug this
> > because I've run out of ideas...
>
> My guess is that some process (systemd?) is configured to unmount that
> directory if anything shows up mounted on it. So when the mount
> propogates it gets unmounted and then the unmount propogates as well.
>
Ah yes! I'd forgotten that I previously had experimented with a mount
unit file for that directory and didn't realize that systemd would
actively prevent anything from being mounted at that point even if the
mount unit was inactive.
Turning up systemd's log level showed the following:
Sep 30 06:59:28 hobo systemd[279]: mnt-puppy.mount changed dead -> mounted
Sep 30 06:59:28 hobo systemd[1]: mnt-puppy.mount changed dead -> mounted
Sep 30 06:59:28 hobo systemd[1]: Unit mnt-puppy.mount is bound to inactive service. Stopping, too.
Sep 30 06:59:28 hobo systemd[1]: Trying to enqueue job mnt-puppy.mount/stop/fail
Sep 30 06:59:28 hobo systemd[1]: Installed new job mnt-puppy.mount/stop as 240
Sep 30 06:59:28 hobo systemd[1]: Enqueued job mnt-puppy.mount/stop as 240
Sep 30 06:59:28 hobo systemd[1]: Unmounting /mnt/puppy...
Sep 30 06:59:28 hobo systemd[1]: About to execute: /bin/umount -n /mnt/puppy
Thanks for pointing me in the right direction!
--
Ross Lagerwall
prev parent reply other threads:[~2014-09-30 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 23:31 Ross Lagerwall
2014-09-29 23:30 ` Eric W. Biederman
2014-09-30 17:46 ` Ross Lagerwall [this message]
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=20140930174655.GB10601@hobo.lan \
--to=rosslagerwall@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®