From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Using mount -o bind vs mount -o subvol=vol
Date: Sat, 3 May 2014 17:47:32 -0700 [thread overview]
Message-ID: <20140504004732.GE9061@merlins.org> (raw)
Is there any functional difference between
mount -o subvol=usr /dev/sda1 /usr
and
mount /dev/sda1 /mnt/btrfs_pool
mount -o bind /mnt/btrfs_pool/usr /usr
?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next reply other threads:[~2014-05-04 5:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 0:47 Marc MERLIN [this message]
2014-05-04 7:07 ` Using mount -o bind vs mount -o subvol=vol Brendan Hide
2014-05-05 0:56 ` Marc MERLIN
2014-05-05 4:13 ` Brendan Hide
2014-05-05 4:36 ` Roman Mamedov
2014-05-05 6:55 ` Brendan Hide
2014-05-06 17:34 ` Duncan
2014-05-05 5:22 ` Marc MERLIN
2014-05-05 2:12 ` Duncan
2014-05-07 10:55 ` Marc MERLIN
2014-05-07 12:31 ` Duncan
2014-05-05 13:54 ` Chris Mason
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=20140504004732.GE9061@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).