Add printing of inode transid and dir item data field.

Signed-off-by: Alexander Block <abloc...@googlemail.com>
---
 print-tree.c |    9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/print-tree.c b/print-tree.c
index fc134c0..1377732 100644
--- a/print-tree.c
+++ b/print-tree.c
@@ -48,6 +48,12 @@ static int print_dir_item(struct extent_buffer *eb, struct 
btrfs_item *item,
                read_extent_buffer(eb, namebuf, (unsigned long)(di + 1), len);
                printf("\t\tnamelen %u datalen %u name: %.*s\n",
                       name_len, data_len, len, namebuf);
+               if (data_len) {
+                       len = (data_len <= sizeof(namebuf))? data_len: 
sizeof(namebuf);
+                       read_extent_buffer(eb, namebuf,
+                               (unsigned long)(di + 1) + name_len, len);
+                       printf("\t\tdata %.*s\n", len, namebuf);
+               }
                len = sizeof(*di) + name_len + data_len;
                di = (struct btrfs_dir_item *)((char *)di + len);
                cur += len;
@@ -481,8 +487,9 @@ void btrfs_print_leaf(struct btrfs_root *root, struct 
extent_buffer *l)
                switch (type) {
                case BTRFS_INODE_ITEM_KEY:
                        ii = btrfs_item_ptr(l, i, struct btrfs_inode_item);
-                       printf("\t\tinode generation %llu size %llu block group 
%llu mode %o links %u\n",
+                       printf("\t\tinode generation %llu transid %llu size 
%llu block group %llu mode %o links %u\n",
                               (unsigned long long)btrfs_inode_generation(l, 
ii),
+                              (unsigned long long)btrfs_inode_transid(l, ii),
                               (unsigned long long)btrfs_inode_size(l, ii),
                               (unsigned long 
long)btrfs_inode_block_group(l,ii),
                               btrfs_inode_mode(l, ii),
-- 
1.7.10

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to