All of lore.kernel.org
 help / color / mirror / Atom feed
From: Isaac Dunham <ibid.ag@gmail.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: mount existing tmpfs mounts a new tmpfs
Date: Mon, 22 Jun 2015 07:49:03 -0700	[thread overview]
Message-ID: <20150622144903.GA1595@localhost> (raw)
In-Reply-To: <55876C53.7030505@ubuntu.com>

On Sun, Jun 21, 2015 at 10:00:51PM -0400, Phillip Susi wrote:

> Forwarding this from debian bug #772419: Run mount /run, and it mounts
> a new tmpfs over top of the existing one in /run ( even if /run isn't
> listed in /etc/fstab ), hiding the existing files.  It should say that
> it is already mounted.

Devuan Jessie, mount 2.26.2-6+devuan1, only says that /run is not in
/etc/fstab unless I use:
 mount -t tmpfs tmpfs /run

The "filesystem mounted or mountpoint busy" stuff should be from
getting errno == EBUSY; this won't happen if you use a virtual filesystem
that supports multiple instances.

*As far as I know*, the only way mount with a single argument is
able to determine the correct filesystem or mountpoint without reading
/etc/fstab is if you add the "remount" option.

HTH,
Isaac Dunham
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in

      parent reply	other threads:[~2015-06-22 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  2:00 mount existing tmpfs mounts a new tmpfs Phillip Susi
2015-06-22  7:09 ` Tom Yan
2015-06-22  8:20 ` Karel Zak
2015-06-22 12:55   ` Ruediger Meier
2015-06-22 14:15     ` Karel Zak
2015-06-22 18:45       ` Phil Susi
2015-06-22 18:45         ` Phil Susi
2015-06-23  9:44         ` Tom Yan
2015-06-23  9:44           ` Tom Yan
2015-06-22 13:31   ` Phil Susi
2015-06-22 14:49 ` Isaac Dunham [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=20150622144903.GA1595@localhost \
    --to=ibid.ag@gmail.com \
    --cc=psusi@ubuntu.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.