From: Shriramana Sharma <samjnaa@gmail.com>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Moving an entire subvol?
Date: Sun, 30 Nov 2014 15:57:06 +0530 [thread overview]
Message-ID: <CAH-HCWW9LQgTc-rhfbbLJBvGu7uCAFiTr_VJ0c=H_ZjYjDW5gA@mail.gmail.com> (raw)
In-Reply-To: <20141130042123.GD8916@merlins.org>
On Sun, Nov 30, 2014 at 9:51 AM, Marc MERLIN <marc@merlins.org> 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
Sorry if my question wasn't clear: I wanted to know how to move a
subvol to appear under another subvol other than its original parent.
Turns out that sudo mv @ @home target/ is quite sufficient. If so why
would the Ubuntu wiki require that set-default not be used? Just @
@home need to be moved to the new place, no?
> Note that you can't mount subvols recursively in one mount AFAIK.
I'm not sure what you mean. I have a few subvols in my external HDD
which is entirely formatted as BtrFS and if I just mount the external
HDD /dev/sdc1 I am able to access all the subvols' contents as well.
--
Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा
next prev parent reply other threads:[~2014-11-30 10:27 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
2014-11-30 10:27 ` Shriramana Sharma [this message]
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='CAH-HCWW9LQgTc-rhfbbLJBvGu7uCAFiTr_VJ0c=H_ZjYjDW5gA@mail.gmail.com' \
--to=samjnaa@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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.