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: Chris Mason <clm@fb.com>
This commit is contained in:
parent
34441361c4
commit
e5d6b12fe1
|
@ -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))) { \
|
||||||
WARN(1, KERN_DEBUG \
|
if ((errno) != -EIO) { \
|
||||||
"BTRFS: Transaction aborted (error %d)\n", \
|
WARN(1, KERN_DEBUG \
|
||||||
(errno)); \
|
"BTRFS: Transaction aborted (error %d)\n", \
|
||||||
|
(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)); \
|
||||||
|
|
Loading…
Reference in New Issue