From: Karel Zak <kzak@redhat.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: util-linux@vger.kernel.org
Subject: Re: Mount -a and bind mounts. Bug?
Date: Fri, 9 Dec 2011 13:48:37 +0100 [thread overview]
Message-ID: <20111209124837.GA7960@nb.net.home> (raw)
In-Reply-To: <20111209123357.GA3173@golden.localdomain>
On Fri, Dec 09, 2011 at 12:33:58PM +0000, Andrew Walrond wrote:
> When using bind mounts, particularly when they are specified in
> /etc/fstab, 'mount -a' does not recognise that a mount is already
> mounted and will rebind another copy over the top with each mount
> -a.
>
> Is this the expected behaviour? I'm not sure so I thought I'd ask.
> I'm using v2.20.1.
- distro?
- linked with libmount?
- do you have regular mtab or symlink to /proc/mounts
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-12-09 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 12:33 Mount -a and bind mounts. Bug? Andrew Walrond
2011-12-09 12:48 ` Karel Zak [this message]
2011-12-09 12:55 ` Andrew Walrond
2011-12-09 13:01 ` Karel Zak
2011-12-09 13:03 ` Karel Zak
2011-12-09 13:15 ` Andrew Walrond
2011-12-09 12:50 ` Andrew Walrond
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=20111209124837.GA7960@nb.net.home \
--to=kzak@redhat.com \
--cc=andrew@walrond.org \
--cc=util-linux@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