diff options
author | Brian Foster <bfoster@redhat.com> | 2020-05-06 13:25:21 -0700 |
---|---|---|
committer | Darrick J. Wong <darrick.wong@oracle.com> | 2020-05-07 08:27:46 -0700 |
commit | 61948b6fb276ad95ad63f82863e607719a31a628 (patch) | |
tree | b62dd5fc36f4e79a44df80b8e8e55769301e2f22 /fs/btrfs/super.c | |
parent | f9bccfcc3b59b9aba64791ab3a2bfefe681ab75b (diff) | |
download | linux-61948b6fb276ad95ad63f82863e607719a31a628.tar.gz linux-61948b6fb276ad95ad63f82863e607719a31a628.tar.bz2 linux-61948b6fb276ad95ad63f82863e607719a31a628.zip |
xfs: ratelimit unmount time per-buffer I/O error alert
At unmount time, XFS emits an alert for every in-core buffer that
might have undergone a write error. In practice this behavior is
probably reasonable given that the filesystem is likely short lived
once I/O errors begin to occur consistently. Under certain test or
otherwise expected error conditions, this can spam the logs and slow
down the unmount.
Now that we have a ratelimit mechanism specifically for buffer
alerts, reuse it for the per-buffer alerts in xfs_wait_buftarg().
Also lift the final repair message out of the loop so it always
prints and assert that the metadata error handling code has shut
down the fs.
Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Allison Collins <allison.henderson@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'fs/btrfs/super.c')
0 files changed, 0 insertions, 0 deletions