From: Sebastian Ochmann <ochmann@informatik.uni-bonn.de>
To: Chris Murphy <lists@colorremedies.com>, zhe.zhang.research@gmail.com
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Is it safe to mount subvolumes of already-mounted volumes (even with different options)?
Date: Thu, 17 Jul 2014 09:58:10 +0200 [thread overview]
Message-ID: <53C78212.2070204@informatik.uni-bonn.de> (raw)
In-Reply-To: <E49EC0AC-DD96-4D7F-9B36-9E28CEC0CD2A@colorremedies.com>
Hello,
I need to clarify, I'm _not_ sharing a drive between multiple computers
at the _same_ time. It's a portable device which I use at different
locations with different computers. I just wanted to give a rationale
for mounting the whole drive to some mountpoint and then also part of
that drive (a subvolume) to the respective computer's /home mountpoint.
So it's controlled by the same kernel in the same computer, it's just
that part of the filesystem is mounted at multiple mountpoints, much
like a bind-mount, but I'm interested in mounting a subvolume of the
already-mounted volume to some other mountpoint. Sorry for the confusion.
Best regards
Sebastian
On 17.07.2014 01:18, Chris Murphy wrote:
>
> On Jul 16, 2014, at 4:18 PM, Sebastian Ochmann <ochmann@informatik.uni-bonn.de> wrote:
>
>> Hello,
>>
>> I'm sharing a btrfs-formatted drive between multiple computers and each of the machines has a separate home directory on that drive.
>
> 2+ computers writing to the same block device? I don't see how this is safe. Seems possibly a bug that the 1st mount event isn't setting some metadata so that another kernel instance knows not to allow another mount.
>
>
> Chris Murphy
>
next prev parent reply other threads:[~2014-07-17 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 22:18 Is it safe to mount subvolumes of already-mounted volumes (even with different options)? Sebastian Ochmann
2014-07-16 23:18 ` Chris Murphy
2014-07-17 7:58 ` Sebastian Ochmann [this message]
2014-07-17 8:48 ` Qu Wenruo
2014-07-17 3:27 ` Zhe Zhang
2014-07-17 8:41 ` Hugo Mills
2014-07-17 15:45 ` Duncan
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=53C78212.2070204@informatik.uni-bonn.de \
--to=ochmann@informatik.uni-bonn.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=zhe.zhang.research@gmail.com \
/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).