aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorYe Bin <yebin10@huawei.com>2023-09-04 18:58:16 +0800
committerTheodore Ts'o <tytso@mit.edu>2023-10-05 22:32:15 -0400
commit71cd5a5aa0607073adba3852739b7f8c22bc7b50 (patch)
tree4086897aa5e2cac5d2bb83f0eeff3e9c29e8a489
parentext4: remove unnecessary initialization of count2 in set_flexbg_block_bitmap (diff)
downloadwireguard-linux-71cd5a5aa0607073adba3852739b7f8c22bc7b50.tar.xz
wireguard-linux-71cd5a5aa0607073adba3852739b7f8c22bc7b50.zip
jbd2: print io_block if check data block checksum failed when do recovery
Now, if check data block checksum failed only print data's block number then skip write data. However, one data block may in more than one transaction. In some scenarios, offline analysis is inconvenient. As a result, it is difficult to locate the areas where data is faulty. So print 'io_block' if check data block checksum failed. Signed-off-by: Ye Bin <yebin10@huawei.com> Reviewed-by: Jan Kara <jack@suse.cz> Link: https://lore.kernel.org/r/20230904105817.1728356-2-yebin10@huawei.com Signed-off-by: Theodore Ts'o <tytso@mit.edu>
-rw-r--r--fs/jbd2/recovery.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/jbd2/recovery.c b/fs/jbd2/recovery.c
index c269a7d29a46..11380ff1fe51 100644
--- a/fs/jbd2/recovery.c
+++ b/fs/jbd2/recovery.c
@@ -661,7 +661,8 @@ static int do_one_pass(journal_t *journal,
printk(KERN_ERR "JBD2: Invalid "
"checksum recovering "
"data block %llu in "
- "log\n", blocknr);
+ "journal block %lu\n",
+ blocknr, io_block);
block_error = 1;
goto skip_write;
}