Add two paragraphs which list some advantages of multipath and explain the benefit for single path devices. The text has been partly composed by Benjamin Marzinski. - Refer to https://www.redhat.com/archives/dm-devel/2020-September/msg00431.html Signed-off-by: Frank Meinl <frank.meinl@xxxxxxx> --- multipath/multipath.8 | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/multipath/multipath.8 b/multipath/multipath.8 index 5b29a5d9..a580630a 100644 --- a/multipath/multipath.8 +++ b/multipath/multipath.8 @@ -89,7 +89,20 @@ multipath \- Device mapper target autoconfig. .\" ---------------------------------------------------------------------------- . .B multipath -is used to detect and coalesce multiple paths to devices, for fail-over or performance reasons. +is used to detect and coalesce multiple paths to devices, for fail-over or +performance reasons. +.PP +.B multipath +works with devices as they are, instead of needing special metadata, like +\fBlvm\fR devices. Plus, multipath deals with devices that have partitions or +logical volumes on top of them. Consequently, multipath can be easily employed +after the device is already set up, without the need to alter logical volumes +or partition tables. +.PP +Despite its name, \fBmultipath\fR may be useful for single path devices, too. +It offers the possibility to queue I/O if no path to the physical device is +available. With queuing, a running application may tolerate a temporary device +disconnect, because outstanding I/O will not fail immediately. . .\" ---------------------------------------------------------------------------- .SH ARGUMENTS -- 2.25.1 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
