[dm-devel] [PATCH 36/42] Clarify dev_loss_tmo capping in multipath.conf.5
Hannes Reinecke
hare at suse.de
Tue Jan 8 13:54:14 UTC 2013
The linux kernel will not allow any dev_loss_tmo setting larger
than 300 if fast_io_fail is not set. So we should document this
in the manpage.
Signed-off-by: Hannes Reinecke <hare at suse.de>
---
multipath/multipath.conf.5 | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
index 247cdc0..35021f6 100644
--- a/multipath/multipath.conf.5
+++ b/multipath/multipath.conf.5
@@ -342,6 +342,8 @@ retry interval
\fIno_path_retry\fR * \fIpolling_interval\fR
if a number of retries is given with \fIno_path_retry\fR and the
overall retry interval is longer than the specified \fIdev_loss_tmo\fR value.
+The linux kernel will cap this value to \fI300\fR if \fBfast_io_fail_tmo\fR
+is not set.
.TP
.B queue_without_daemon
If set to
--
1.7.4.2
More information about the dm-devel
mailing list