diff options
author | Christoph Hellwig <hch@lst.de> | 2017-01-09 13:41:33 -0800 |
---|---|---|
committer | Darrick J. Wong <darrick.wong@oracle.com> | 2017-01-09 13:45:01 -0800 |
commit | 84a4620cfe97c9d57e39b2369bfb77faff55063d (patch) | |
tree | 4d64448c06bdf88721c6a01fd626386d73ea785e /lib/locking-selftest-rlock-hardirq.h | |
parent | 12ef830198b0d71668eb9b59f9ba69d32951a48a (diff) | |
download | op-kernel-dev-84a4620cfe97c9d57e39b2369bfb77faff55063d.zip op-kernel-dev-84a4620cfe97c9d57e39b2369bfb77faff55063d.tar.gz |
xfs: don't print warnings when xfs_log_force fails
There are only two reasons for xfs_log_force / xfs_log_force_lsn to fail:
one is an I/O error, for which xlog_bdstrat already logs a warning, and
the second is an already shutdown log due to a previous I/O errors. In
the latter case we'll already have a previous indication for the actual
error, but the large stream of misleading warnings from xfs_log_force
will probably scroll it out of the message buffer.
Simply removing the warnings thus makes the XFS log reporting significantly
better.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'lib/locking-selftest-rlock-hardirq.h')
0 files changed, 0 insertions, 0 deletions