Blame SOURCES/0051-multipath.conf.5-Improve-checker_timeout-description.patch

b7337d
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
b7337d
From: Benjamin Marzinski <bmarzins@redhat.com>
b7337d
Date: Tue, 15 Dec 2020 12:47:14 -0600
b7337d
Subject: [PATCH] multipath.conf.5: Improve checker_timeout description
b7337d
b7337d
I was asked to explain how checker_timeout works for checkers like
b7337d
directio, that don't issue scsi commands with an explicit timeout
b7337d
b7337d
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
b7337d
---
b7337d
 multipath/multipath.conf.5 | 9 +++++++--
b7337d
 1 file changed, 7 insertions(+), 2 deletions(-)
b7337d
b7337d
diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
b7337d
index 60954574..a5686090 100644
b7337d
--- a/multipath/multipath.conf.5
b7337d
+++ b/multipath/multipath.conf.5
b7337d
@@ -634,8 +634,13 @@ The default is: \fBno\fR
b7337d
 .
b7337d
 .TP
b7337d
 .B checker_timeout
b7337d
-Specify the timeout to use for path checkers and prioritizers that issue SCSI
b7337d
-commands with an explicit timeout, in seconds.
b7337d
+Specify the timeout to use for path checkers and prioritizers, in seconds.
b7337d
+Only prioritizers that issue scsi commands use checker_timeout. Checkers
b7337d
+that support an asynchronous mode (\fItur\fR and \fIdirectio\fR), will
b7337d
+return shortly after being called by multipathd, regardless of whether the
b7337d
+storage array responds. If the storage array hasn't responded, mulitpathd will
b7337d
+check for a response every second, until \fIchecker_timeout\fR seconds have
b7337d
+elapsed.
b7337d
 .RS
b7337d
 .TP
b7337d
 The default is: in \fB/sys/block/sd<x>/device/timeout\fR
b7337d
-- 
b7337d
2.17.2
b7337d