From: "Guenther Rasch" <Guenther.Rasch@FernUni-Hagen.de>
To: linux-btrfs@vger.kernel.org
Subject: Question about btrfs metadata structure
Date: Wed, 25 Jul 2012 12:41:15 +0200 [thread overview]
Message-ID: <web-48902846@mailstore.fernuni-hagen.de> (raw)
Hi!
I'm writing my bsc thesis about btrfs and I'm analyzing
the
btrfs metadata structure at the moment.
I'm using fedora 17 with kernel 3.4 and btrfs-prog from
your
git-repository. For an overview I use "btrfs-debug-tree"
and
here are my questions:
The root tree contains some inode_items, but I don't
understand
the meaning of them:
item 4 key (ROOT_TREE_DIR INODE_ITEM 0) itemoff 3101
itemsize 160
inode generation 3 size 0 block group 0 mode 40555 links 1
item 5 key (ROOT_TREE_DIR INODE_REF 6) itemoff 3089
itemsize 12
inode ref index 0 namelen 2 name: ..
The key for an inode_item is objectid=ROOT_TREE_DIR.
ROOT-TREE-DIR is the inode-Nr.?
What does offset=6 regarding INODE_REF mean? --> item 5
Also placed in the root tree, I've found entries of
(FREE_SPACE UNTYPED ....)
What does UNTYPED mean in this context and the offset is
the logical address of a block group (I guess...)? This
item has a pointer to an inode_item, is that right?
And last question about this entries:
item 2 key (FS_TREE INODE_REF 6) itemoff 3500 itemsize 17
inode ref index 0 namelen 7 name: default
...
item 6 key (ROOT_TREE_DIR DIR_ITEM 2378154706) itemoff
3052 itemsize 37
location key (FS_TREE ROOT_ITEM 18446744073709551615)
type 2
namelen 7 datalen 0 name: default
There is an INODE_REF (again, offset 6...?) pointing to
which inode? I cannot find some...
What's about that offset in location key (FS_TREE....)
Thx in advance for your patience and answers!
Regards
Guenther
next reply other threads:[~2012-07-25 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 10:41 Guenther Rasch [this message]
2012-07-27 7:07 ` Question about btrfs metadata structure Guenther Rasch
2012-07-27 7:21 ` Guenther Rasch
2012-07-27 7:34 ` Liu Bo
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=web-48902846@mailstore.fernuni-hagen.de \
--to=guenther.rasch@fernuni-hagen.de \
--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).