From: josef@toxicpanda.com
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: Josef Bacik <jbacik@fb.com>
Subject: [PATCH][v2] btrfs-progs: print the csum length in debug-tree
Date: Fri, 25 Aug 2017 11:11:46 -0400 [thread overview]
Message-ID: <1503673906-14342-1-git-send-email-jbacik@fb.com> (raw)
From: Josef Bacik <jbacik@fb.com>
While looking at a log of a corrupted fs I needed to verify we were
missing csums for a given range. Make this easier by printing out the
range of bytes a csum item covers.
Signed-off-by: Josef Bacik <jbacik@fb.com>
---
v1->v2:
- print the byte range instead of just the length
print-tree.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/print-tree.c b/print-tree.c
index 5927ed3..2aead6a 100644
--- a/print-tree.c
+++ b/print-tree.c
@@ -1103,9 +1103,16 @@ void btrfs_print_leaf(struct btrfs_root *root, struct extent_buffer *eb)
case BTRFS_CSUM_ITEM_KEY:
printf("\t\tcsum item\n");
break;
- case BTRFS_EXTENT_CSUM_KEY:
- printf("\t\textent csum item\n");
+ case BTRFS_EXTENT_CSUM_KEY: {
+ u16 csum_size =
+ btrfs_super_csum_size(root->fs_info->super_copy);
+ u32 size = (item_size / csum_size) *
+ root->fs_info->sectorsize;
+ printf("\t\textent csum item range %llu-%llu\n",
+ (unsigned long long)disk_key.offset,
+ (unsigned long long)disk_key.offset + size);
break;
+ }
case BTRFS_EXTENT_DATA_KEY:
print_file_extent_item(eb, item, i, ptr);
break;
--
2.7.4
next reply other threads:[~2017-08-25 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 15:11 josef [this message]
2017-08-25 15:17 ` [PATCH][v2] btrfs-progs: print the csum length in debug-tree Nikolay Borisov
2017-09-01 15:29 ` 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=1503673906-14342-1-git-send-email-jbacik@fb.com \
--to=josef@toxicpanda.com \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--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 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.