From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: howto create subvolume at top level?
Date: Mon, 1 Jun 2015 18:01:58 +0000 (UTC) [thread overview]
Message-ID: <pan$2fa54$a3a0c7f9$fa61118f$2f8df70c@cox.net> (raw)
In-Reply-To: pan$bc8b8$574d5213$341e3921$d2025f4a@cox.net
Duncan posted on Mon, 01 Jun 2015 17:51:19 +0000 as excerpted:
>> 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/.
OK, I see now, you already have a subvolume called root, that's not ID5,
the root (aka top level ID5) subvolume. Thus it's ID 257. Fine
distinction.
Calvin W is correct. Mount the top level subvolume and create there.
What you're doing now is actually what I suggested with the nesting, and
your "root" subvolume <> the top-level ID5 subvolume. I'll claim just
waking up and not having my caffeine yet. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-06-01 18:02 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 [this message]
2015-06-01 18:08 ` Neal Becker
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='pan$2fa54$a3a0c7f9$fa61118f$2f8df70c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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