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

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