mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2024-12-27 11:29:36 +03:00
2959d94a0a
ZFS works best when it is notified as soon as possible when a device failure occurs. This allows it to immediately start any recovery actions which may be needed. In theory Linux supports a flag which can be set on bio's called FAILFAST which provides this quick notification by disabling the retry logic in the lower scsi layers. That's the theory at least. In practice is turns out that while the flag exists you oddly have to set it with the BIO_RW_AHEAD flag. And even when it's set it you may get retries in the low level drivers decides that's the right behavior, or if you don't get the right error codes reported to the scsi midlayer. Unfortunately, without additional kernels patchs there's not much which can be done to improve this. Basically, this just means that it may take 2-3 minutes before a ZFS is notified properly that a device has failed. This can be improved and I suspect I'll be submitting patches upstream to handle this.
23 lines
579 B
Plaintext
23 lines
579 B
Plaintext
dnl #
|
|
dnl # 2.6.28 API change
|
|
dnl # Device, transport, and driver FAILFAST flags were added and
|
|
dnl # the now legacy BIO_RW_FAILFAST flag was removed.
|
|
dnl #
|
|
AC_DEFUN([ZFS_AC_KERNEL_BIO_FAILFAST], [
|
|
AC_MSG_CHECKING([whether BIO_RW_FAILFAST_* are defined])
|
|
ZFS_LINUX_TRY_COMPILE([
|
|
#include <linux/bio.h>
|
|
],[
|
|
int flags;
|
|
flags = ((1 << BIO_RW_FAILFAST_DEV) |
|
|
(1 << BIO_RW_FAILFAST_TRANSPORT) |
|
|
(1 << BIO_RW_FAILFAST_DRIVER));
|
|
],[
|
|
AC_MSG_RESULT(yes)
|
|
AC_DEFINE(HAVE_BIO_RW_FAILFAST, 1,
|
|
[BIO_RW_FAILFAST_* are defined])
|
|
],[
|
|
AC_MSG_RESULT(no)
|
|
])
|
|
])
|