Commit f1d486a3 authored by Dave Chinner's avatar Dave Chinner Committed by Alex Elder

xfs: don't warn on EAGAIN in inode reclaim

Any inode reclaim flush that returns EAGAIN will result in the inode
reclaim being attempted again later. There is no need to issue a
warning into the logs about this situation.
Signed-off-by: default avatarDave Chinner <dchinner@redhat.com>
Reviewed-by: default avatarAlex Elder <aelder@sgi.com>
Signed-off-by: default avatarAlex Elder <aelder@sgi.com>
parent b6f8dd49
...@@ -820,10 +820,10 @@ xfs_reclaim_inode( ...@@ -820,10 +820,10 @@ xfs_reclaim_inode(
* call into reclaim to find it in a clean state instead of waiting for * call into reclaim to find it in a clean state instead of waiting for
* it now. We also don't return errors here - if the error is transient * it now. We also don't return errors here - if the error is transient
* then the next reclaim pass will flush the inode, and if the error * then the next reclaim pass will flush the inode, and if the error
* is permanent then the next sync reclaim will relcaim the inode and * is permanent then the next sync reclaim will reclaim the inode and
* pass on the error. * pass on the error.
*/ */
if (error && !XFS_FORCED_SHUTDOWN(ip->i_mount)) { if (error && error != EAGAIN && !XFS_FORCED_SHUTDOWN(ip->i_mount)) {
xfs_fs_cmn_err(CE_WARN, ip->i_mount, xfs_fs_cmn_err(CE_WARN, ip->i_mount,
"inode 0x%llx background reclaim flush failed with %d", "inode 0x%llx background reclaim flush failed with %d",
(long long)ip->i_ino, error); (long long)ip->i_ino, error);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment