Commit e5d6b12f authored by Chris Mason's avatar Chris Mason

Btrfs: don't WARN() in btrfs_transaction_abort() for IO errors

btrfs_transaction_abort() has a WARN() to help us nail down whatever
problem lead to the abort.  But most of the time, we're aborting for EIO,
and the warning just adds noise.
Signed-off-by: default avatarChris Mason <clm@fb.com>
parent 34441361
...@@ -3445,9 +3445,14 @@ do { \ ...@@ -3445,9 +3445,14 @@ do { \
/* Report first abort since mount */ \ /* Report first abort since mount */ \
if (!test_and_set_bit(BTRFS_FS_STATE_TRANS_ABORTED, \ if (!test_and_set_bit(BTRFS_FS_STATE_TRANS_ABORTED, \
&((trans)->fs_info->fs_state))) { \ &((trans)->fs_info->fs_state))) { \
if ((errno) != -EIO) { \
WARN(1, KERN_DEBUG \ WARN(1, KERN_DEBUG \
"BTRFS: Transaction aborted (error %d)\n", \ "BTRFS: Transaction aborted (error %d)\n", \
(errno)); \ (errno)); \
} else { \
pr_debug("BTRFS: Transaction aborted (error %d)\n", \
(errno)); \
} \
} \ } \
__btrfs_abort_transaction((trans), __func__, \ __btrfs_abort_transaction((trans), __func__, \
__LINE__, (errno)); \ __LINE__, (errno)); \
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment