From: Martin Wilck <[email protected]>
The paragraph stating that the san_path_err algorithm is deprecated
has been moved into the FPIN section by mistake.
Move it upward, and use a weaker wording. While the san_path_err algorithm is
technical inferior to the marginal_path approach, it is also easier to
understand and set up. Furthermore, we documented that it's the replacement
for the delay_check algorithm. Therefore the strong "deprecated" wording is
exaggerated.
Fixes: cfff03e ("multipathd: handle fpin events")
Signed-off-by: Martin Wilck <[email protected]>
Cc: Xose Vazquez Perez <[email protected]>
Cc: Muneendra Kumar <[email protected]>
---
multipath/multipath.conf.5 | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
index bd7d778..41a0112 100644
--- a/multipath/multipath.conf.5
+++ b/multipath/multipath.conf.5
@@ -1877,18 +1877,19 @@ increase and the threshold is never reached. Ticks are
the time between
path checks by multipathd, which is variable and controlled by the
\fIpolling_interval\fR and \fImax_polling_interval\fR parameters.
.
+.RS 8
+.LP
+This algorithm is superseded by the \(dqmarginal_path\(dq failure tracking,
+but remains supported for backward compatibility.
+.
+.RE
.TP
-.B \(dqFPIN \(dq failure tracking
+.B \(dqFPIN\(dq failure tracking
Fibre channel fabrics can notify hosts about fabric-level issues such
as integrity failures or congestion with so-called Fabric Performance
Impact Notifications (FPINs).On receiving the fpin notifications through ELS
multipathd will move the affected path and port states to marginal.
.
-.RS 8
-.LP
-This method is \fBdeprecated\fR in favor of the \(dqmarginal_path\(dq failure
-tracking method, and only offered for backward compatibility.
-.
.RE
.LP
See the documentation
--
2.38.1
--
dm-devel mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/dm-devel
