From: sri <toyours_sridhar@yahoo.co.in>
To: linux-btrfs@vger.kernel.org
Subject: how many chunk trees and extent trees present
Date: Fri, 17 Apr 2015 06:24:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20150417T081705-332@post.gmane.org> (raw)
Hi,
I have below queries. Could somebody help me in understanding.
1)
As per my understanding btrfs file system uses one chunk tree and one
extent tree for entire btrfs disk allocation.
Is this correct?
In, some article i read that future there will be more chunk tree/ extent
tree for single btrfs. Is this true.
If yes, I would like to know why more than one chunk / extent tree is
required to represent one btrfs file system.
2)
Also I would like to know for a subvolume / snapshot , is there a
provision to ask btrfs , represent all blocks belongs to that
subvolume/snapshot should handle with a separate chunk tree and extent
tree?
I am looking for a way to traverse a subvolume preferably a snapshot and
identify all disk blocks (extents) allocated for that particular subvolume
/ snapshot.
next reply other threads:[~2015-04-17 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 6:24 sri [this message]
2015-04-17 9:19 ` how many chunk trees and extent trees present Hugo Mills
2015-04-17 9:56 ` sri
2016-02-25 12:16 ` sri
2016-02-26 1:21 ` Qu Wenruo
2015-04-17 17:29 ` David Sterba
2016-02-26 1:29 ` Qu Wenruo
2016-03-03 10:02 ` David Sterba
2016-03-04 2:58 ` Anand Jain
2016-03-04 9:26 ` 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=loom.20150417T081705-332@post.gmane.org \
--to=toyours_sridhar@yahoo.co.in \
--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;
as well as URLs for NNTP newsgroup(s).