Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: root subvol id is 0 or 5?
Date: Mon, 1 Dec 2014 03:49:34 +0000 (UTC)	[thread overview]
Message-ID: <pan$ce947$5d255e02$2716ded9$f6df99fd@cox.net> (raw)
In-Reply-To: 20141130135328.GG32735@carfax.org.uk

Hugo Mills posted on Sun, 30 Nov 2014 13:53:28 +0000 as excerpted:

> On Sun, Nov 30, 2014 at 07:08:51PM +0530, Shriramana Sharma wrote:
>> On Sun, Nov 30, 2014 at 5:29 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>> >
>> >    In the data structures on disk, it's 5. The kernel aliases 0 to
>> > mean subvolid 5.
>> 
>> So why 5 and not just 0 which seems a logical choice? On top of this,
>> one needs to alias 0 to 5!
> 
>    All of the trees used in the FS metadata have an ID number. The
> "well-known" trees have small, fixed IDs:

Thanks, Hugo.

You might wish to find a place in the wiki (probably in the FAQ) for 
that, since your explanation was both the clearest I can imagine and 
cleared up some lingering "but why?" questions along that line for me, as 
well.

And if an answer to that basic a btrfs question is still clearing stuff 
up for me, I expect it could be useful to well over 90% of potential 
btrfs wiki FAQ readers...

-- 
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


      reply	other threads:[~2014-12-01  3:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30  3:31 root subvol id is 0 or 5? Shriramana Sharma
2014-11-30  7:48 ` Goffredo Baroncelli
2014-11-30 11:59 ` Hugo Mills
2014-11-30 13:38   ` Shriramana Sharma
2014-11-30 13:42     ` Shriramana Sharma
2015-02-27 16:50       ` David Sterba
2014-11-30 13:53     ` Hugo Mills
2014-12-01  3:49       ` Duncan [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='pan$ce947$5d255e02$2716ded9$f6df99fd@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