From: Neal Becker <ndbecker2@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: howto create subvolume at top level?
Date: Mon, 01 Jun 2015 14:08:52 -0400 [thread overview]
Message-ID: <mki73l$h7g$1@ger.gmane.org> (raw)
In-Reply-To: pan$bc8b8$574d5213$341e3921$d2025f4a@cox.net
Duncan wrote:
> Neal Becker posted on Mon, 01 Jun 2015 13:25:52 -0400 as excerpted:
>
>> [nbecker@nbecker2 ~]$ sudo btrfs subvolume create /home2
>> Create subvolume '//home2'
>> [nbecker@nbecker2 ~]$ sudo btrfs subvolume list /
>> ID 257 gen 66376 top level 5 path root
>> ID 316 gen 66376 top level 257 path home2
>>
>> This created home2 under root. How do I create home2 with top level as
>> top level 5, at the same level as root?
>>
>> IOW:
>>
>> ID 257 gen 66376 top level 5 path root
>> ID 316 gen 66376 top level 5 path home2
>
> Briefly stated, you don't. Just like / is the top of a Unix style
> directory tree, the root subvolume is the top of a btrfs subvolume tree.
> You can't go higher than that, and that's what the top level /is/.
>
> But what are you actually trying to do? You _can_ change the default
> subvolume pointer so a subvolume other than root/5 is mounted by default,
> and you can nest subvolumes, so for most purposes, you can /pretend/ that
> some arbitrarily named subvolume is your top subvolume. Alternatively,
> you can of course mount subvolumes wherever you want in the directory
> tree.
>
> Also see the subvolumes discussion and related FAQs on the wiki if you
> haven't.
>
> https://btrfs.wiki.kernel.org/
>
But I already have a server setup like this, which was created by anaconda:
sudo btrfs subvolume list /
ID 256 gen 1828545 top level 5 path home
ID 259 gen 1818478 top level 5 path root
ID 487 gen 1828544 top level 5 path root00
--
Those who fail to understand recursion are doomed to repeat it
prev parent reply other threads:[~2015-06-01 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 17:25 howto create subvolume at top level? Neal Becker
2015-06-01 17:34 ` Calvin Walton
2015-06-01 17:51 ` Duncan
2015-06-01 18:01 ` Duncan
2015-06-01 18:08 ` Neal Becker [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='mki73l$h7g$1@ger.gmane.org' \
--to=ndbecker2@gmail.com \
--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