iomap: enhance writeback error message

If we encounter an IO error during writeback, log the inode, offset, and
sector number of the failure, instead of forcing the user to do some
sort of reverse mapping to figure out which file is affected.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>

diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index 0fd58adcdeaa58ad4bf1ba8807ec382a7be246a8..55d7efa4fb8cb0f1df7c01422d11644f3159c58d 100644 (file)
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@ -1162,8 +1162,9 @@ iomap_finish_ioend(struct iomap_ioend *ioend, int error)
 
        if (unlikely(error && !quiet)) {
                printk_ratelimited(KERN_ERR
-                       "%s: writeback error on sector %llu",
-                       inode->i_sb->s_id, start);
+"%s: writeback error on inode %lu, offset %lld, sector %llu",
+                       inode->i_sb->s_id, inode->i_ino, ioend->io_offset,
+                       start);
        }
 }