diff options
author | Carlos Maiolino <cmaiolino@redhat.com> | 2016-05-18 11:08:15 +1000 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2016-05-18 11:08:15 +1000 |
commit | a5ea70d25d76950e11690110b526374307d05d81 (patch) | |
tree | 8b131bde696d1ed8e887f4ebcd0a82059ad2eba4 /fs/xfs/xfs_mount.h | |
parent | ef6a50fbb1bba7951aa23adcfb40e99ca72dc51c (diff) | |
download | blackbird-obmc-linux-a5ea70d25d76950e11690110b526374307d05d81.tar.gz blackbird-obmc-linux-a5ea70d25d76950e11690110b526374307d05d81.zip |
xfs: add configuration of error failure speed
On reception of an error, we can fail immediately, perform some
bound amount of retries or retry indefinitely. The current behaviour
we have is to retry forever.
However, we'd like the ability to choose how long the filesystem
should try after an error, it can either fail immediately, retry a
few times, or retry forever. This is implemented by using
max_retries sysfs attribute, to hold the amount of times we allow
the filesystem to retry after an error. Being -1 a special case
where the filesystem will retry indefinitely.
Add both a maximum retry count and a retry timeout so that we can
bound by time and/or physical IO attempts.
Finally, plumb these into xfs_buf_iodone error processing so that
the error behaviour follows the selected configuration.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/xfs/xfs_mount.h')
-rw-r--r-- | fs/xfs/xfs_mount.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/xfs/xfs_mount.h b/fs/xfs/xfs_mount.h index 0c5a97644d78..2fafa9438bcf 100644 --- a/fs/xfs/xfs_mount.h +++ b/fs/xfs/xfs_mount.h @@ -52,9 +52,12 @@ enum { XFS_ERR_ERRNO_MAX, }; +#define XFS_ERR_RETRY_FOREVER -1 + struct xfs_error_cfg { struct xfs_kobj kobj; int max_retries; + unsigned long retry_timeout; /* in jiffies, 0 = no timeout */ }; typedef struct xfs_mount { |