leandrof/linux
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

iomap: enhance writeback error message

Browse Source 
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>
This commit is contained in:
Darrick J. Wong 2019-10-17 14:02:07 -07:00
parent 48d64cd18b
commit 9cd0ed63ca
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
fs/iomap/buffered-io.c
View File

@ -1162,8 +1162,9 @@ iomap_finish_ioend(struct iomap_ioend *ioend, int error)
if (unlikely(error && !quiet)) { if (unlikely(error && !quiet)) {
printk_ratelimited(KERN_ERR printk_ratelimited(KERN_ERR
"%s: writeback error on sector %llu", "%s: writeback error on inode %lu, offset %lld, sector %llu",
inode->i_sb->s_id, start); inode->i_sb->s_id, inode->i_ino, ioend->io_offset,
start);
} }
} }