Message ID | 20191017210110.GP13108@magnolia (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | iomap: enhance writeback error message | expand |
On Thu, Oct 17, 2019 at 02:01:11PM -0700, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@oracle.com> > > 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> Looks good to me. Reviewed-by: Dave Chinner <dchinner@redhat.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c index 0fd58adcdeaa..55d7efa4fb8c 100644 --- 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); } }