aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorJohannes Thumshirn <johannes.thumshirn@wdc.com>2024-07-31 22:43:03 +0200
committerDavid Sterba <dsterba@suse.com>2024-09-10 16:51:17 +0200
commitf8428360c8f9eca3bf355cdf10b789f880d61b47 (patch)
tree2a01b4e487efaf02794092d8a0f7f77b1394f474
parentbtrfs: add comment about locking in cow_file_range_inline() (diff)
downloadwireguard-linux-f8428360c8f9eca3bf355cdf10b789f880d61b47.tar.xz
wireguard-linux-f8428360c8f9eca3bf355cdf10b789f880d61b47.zip
btrfs: don't dump stripe-tree on lookup error
This just creates unnecessary noise and doesn't provide any insights into debugging RAID stripe-tree related issues. Reviewed-by: Josef Bacik <josef@toxicpanda.com> Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
-rw-r--r--fs/btrfs/raid-stripe-tree.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/btrfs/raid-stripe-tree.c b/fs/btrfs/raid-stripe-tree.c
index bd06ff795691..c1c74f310e8b 100644
--- a/fs/btrfs/raid-stripe-tree.c
+++ b/fs/btrfs/raid-stripe-tree.c
@@ -284,8 +284,6 @@ out:
if (ret > 0)
ret = -ENOENT;
if (ret && ret != -EIO && !stripe->is_scrub) {
- if (IS_ENABLED(CONFIG_BTRFS_DEBUG))
- btrfs_print_tree(leaf, 1);
btrfs_err(fs_info,
"cannot find raid-stripe for logical [%llu, %llu] devid %llu, profile %s",
logical, logical + *length, stripe->dev->devid,