--- multipath/multipath.conf.5 | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5 index ab151e720d75..33ad775139c4 100644 --- a/multipath/multipath.conf.5 +++ b/multipath/multipath.conf.5 @@ -954,12 +954,43 @@ device again, as soon as it sees a path with that WWID. This should allow most users to have multipath automatically choose the correct paths to make into multipath devices, without having to edit the blacklist. .RS +.PP +If \fBignore_wwids\fR is set to +.I no +, only method +.I 2 +above (manual creation by the user) will be used for creating new maps. +.RE +.RS .TP The default is: \fBno\fR .RE . . .TP +.B ignore_wwids +If set to +.I no +, multipath and multipathd only consider paths matching a WWID listed in +the \fBwwids_file\fR as valid multipath devices. Automatic multipath map +creation is disabled. +. +If set to +.I yes +, and \fBfind_multipaths\fR is +.I no +, every device which is not blacklisted +will be treated as a potential multipath member. See above for +the logic if \fBfind_multipaths\fR is set to +.I yes. +. +.RS +.TP +The default is: \fBoff\fR +.RE +. +. +.TP .B uxsock_timeout CLI receive timeout in milliseconds. For larger systems CLI commands might timeout before the multipathd lock is released and the CLI command -- 2.15.1 -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
