Hi Zanier,
I didn't get your question exactly but here are some clues.
Don't use "df" command with btrfs (it will lie to you) but use "btrft filesystem df" command insted, but it will not give you the inode.
From WikiPedia:
Quote:
|
User-visible files and directories all live in a file system tree. File and directory objects all have inode items. Extended attributes and ACL entries are stored alongside in separate items.
|
From
https://btrfs.wiki.kernel.org/index...._design#Inodes:
Quote:
|
Inodes are stored in struct btrfs_inode_item at offset zero in the key, and have a type value of one. Inode items are always the lowest valued key for a given object, and they store the traditional stat data for files and directories. The inode structure is relatively small, and will not contain embedded file data or extended attribute data. These things are stored in other item types.
|
From
https://btrfs.wiki.kernel.org/index.php/Changelog (V3.2 bug fix):
Quote:
|
ioctl for resolving logical->inode and inode->path
|
Additional resource (very interesting presentation)
https://www.youtube.com/watch?v=hxWuaozpe2I
I hope that will help,
Angel.
