All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs subvolume list: what is the meaning of "top level"
Date: Sun, 10 Nov 2013 08:38:28 +0100	[thread overview]
Message-ID: <527F37F4.2070904@libero.it> (raw)
In-Reply-To: <35C9C3FD-BB32-4D8E-ADDA-1A5E23923442@colorremedies.com>

On 2013-11-09 21:18, Chris Murphy wrote:
> 
> On Nov 9, 2013, at 11:10 AM, Goffredo Baroncelli <kreijack@inwind.it>
> wrote:
>> 
>> 1	ID 256 gen 5 top level 5 path sub1 2	ID 257 gen 6 top level 5
>> path dir/sub2 3	ID 258 gen 8 top level 5 path dir/sub3 4	ID 259 gen
>> 8 top level 5 path dir/sub3/sub4 5	ID 260 gen 10 top level 5 path
>> sub5 6	ID 261 gen 10 top level 5 path sub5/sub6
> 
>> 
>> 
>> I expected that in the line 4, the top level should be 258; the
>> same for the line 6: top level should be 260. So my question is:
>> what is the meaning of the "top level" value ?
> 
> If you mount -o subvol=sub5 and then create a new subvolume, and then
> do a listing, you'll see something like what you describe. It would
> look something like:
> 
> 6	ID 262 gen 4 top level 260 path sub6
> 
> The "top level" is in a sense a prefix. So top level 5 means there is
> no prefix, the path listed is the full path. Whereas if the top level
> is e.g. 260, the implied prefix is sub5/.

Chris, many thanks, not it is clear.

> 
> If you were to mount subvolid=259 and create a subvolume in at the
> root of the mountpoint, then do a subvolume listing, it would be
> listed with top level 259 and a path of merely "newname" rather than
> dir/sub3/sub4/newname.
> 
> So just consider the top level a prefix for the listed path, and if
> the top level is 5, there is no prefix for path, the path is the full
> path.
> 
> 
> Chris Murphy-- To unsubscribe from this list: send the line
> "unsubscribe linux-btrfs" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> 


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2013-11-10  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09 18:10 btrfs subvolume list: what is the meaning of "top level" Goffredo Baroncelli
2013-11-09 20:18 ` Chris Murphy
2013-11-10  7:38   ` Goffredo Baroncelli [this message]
2013-11-10  7:55     ` Goffredo Baroncelli

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=527F37F4.2070904@libero.it \
    --to=kreijack@libero.it \
    --cc=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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.