From: Marc MERLIN <marc@merlins.org>
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Moving an entire subvol?
Date: Sat, 29 Nov 2014 20:21:23 -0800 [thread overview]
Message-ID: <20141130042123.GD8916@merlins.org> (raw)
In-Reply-To: <CAH-HCWVcu9FW0c3zwEg_KR_yaPGRQ58yHbXsUx1JCKRu4s7NXQ@mail.gmail.com>
On Sun, Nov 30, 2014 at 09:01:42AM +0530, Shriramana Sharma wrote:
> So the Ubuntu Wiki BtrFS entry advises against using subvol
> set-default because it boots its kernel using root=subvol=@ and home
> as subvol=@home, and these two subvols are only present under the
> subvol with ID 5. But isn't it just possible to move i.e. reparent a
> subvol so I can move these two under another subvol and have that as
> default?
Make a new subvolume called /root and just mount subvol=root
Note that you can't mount subvols recursively in one mount AFAIK.
This is what my system looks like:
LABEL=btrfs_pool1 / btrfs subvol=root,defaults,compress=lzo,discard,skip_balance,noatime 0 0
LABEL=btrfs_pool1 /usr btrfs subvol=usr,defaults,compress=lzo,discard,skip_balance,noatime 0 0
LABEL=btrfs_pool1 /var btrfs subvol=var,defaults,compress=lzo,discard,skip_balance,noatime 0 0
LABEL=btrfs_pool1 /home btrfs subvol=home,defaults,compress=lzo,discard,skip_balance,noatime 0 0
LABEL=btrfs_pool1 /tmp btrfs subvol=tmp,defaults,compress=lzo,discard,skip_balance,noatime,noexec 0 0
LABEL=btrfs_pool1 /mnt/btrfs_pool1 btrfs defaults,compress=lzo,discard,skip_balance,noatime,subvolid=0 0 0
Hope this helps.
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 prev parent reply other threads:[~2014-11-30 4:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 3:31 Moving an entire subvol? Shriramana Sharma
2014-11-30 4:21 ` Marc MERLIN [this message]
2014-11-30 10:27 ` Shriramana Sharma
2014-12-01 0:10 ` Marc MERLIN
2014-12-01 0:54 ` Chris Murphy
2014-12-02 3:21 ` Shriramana Sharma
2014-12-02 8:34 ` Hugo Mills
2014-12-03 2:32 ` Shriramana Sharma
2014-12-03 8:37 ` Hugo Mills
2014-12-02 8:50 ` Duncan
2014-12-02 13:28 ` David Sterba
2014-12-02 15:11 ` Shriramana Sharma
2014-12-02 20:30 ` Robert White
2014-12-02 21:13 ` Austin S Hemmelgarn
2014-12-03 2:33 ` Shriramana Sharma
2014-12-05 17:34 ` David Sterba
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=20141130042123.GD8916@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=samjnaa@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