|
 |
4ae388 |
---
|
|
|
4ae388 |
multipath/multipath.conf.5 | 22 ++++++++++++++++++++++
|
|
|
4ae388 |
1 file changed, 22 insertions(+)
|
|
|
4ae388 |
|
|
|
4ae388 |
Index: multipath-tools-130222/multipath/multipath.conf.5
|
|
|
4ae388 |
===================================================================
|
|
|
4ae388 |
--- multipath-tools-130222.orig/multipath/multipath.conf.5
|
|
|
4ae388 |
+++ multipath-tools-130222/multipath/multipath.conf.5
|
|
|
4ae388 |
@@ -84,6 +84,28 @@ directory where the dynamic shared objec
|
|
|
4ae388 |
dependent, commonly
|
|
|
4ae388 |
.I /lib/multipath
|
|
|
4ae388 |
.TP
|
|
|
4ae388 |
+.B find_multipaths
|
|
|
4ae388 |
+If set to
|
|
|
4ae388 |
+.I yes
|
|
|
4ae388 |
+, instead of trying to create a multipath device for every non-blacklisted
|
|
|
4ae388 |
+path, multipath will only create a device if one of three condidions are
|
|
|
4ae388 |
+met.
|
|
|
4ae388 |
+.I 1
|
|
|
4ae388 |
+There are at least two non-blacklisted paths with the same wwid,
|
|
|
4ae388 |
+.I 2
|
|
|
4ae388 |
+the user manually forces the creation, by specifying a device with the multipath
|
|
|
4ae388 |
+command, or
|
|
|
4ae388 |
+.I 3
|
|
|
4ae388 |
+a path has the same WWID as a multipath device that was previously created
|
|
|
4ae388 |
+while find_multipaths was set (even if that multipath device doesn't currently
|
|
|
4ae388 |
+exist).
|
|
|
4ae388 |
+Whenever a multipath device is created with find_multipaths set, multipath will
|
|
|
4ae388 |
+remeber the WWID of the device, so that it will automatically create the
|
|
|
4ae388 |
+device again, as soon as it sees a path with that WWID. This should allow most
|
|
|
4ae388 |
+users to have multipath automatically choose the correct paths to make into
|
|
|
4ae388 |
+multipath devices, without having to edit the blacklist; Default is
|
|
|
4ae388 |
+.I no
|
|
|
4ae388 |
+.TP
|
|
|
4ae388 |
.B verbosity
|
|
|
4ae388 |
default verbosity. Higher values increase the verbosity level. Valid
|
|
|
4ae388 |
levels are between 0 and 6; default is
|