multipath-tools: delete obsolete information from multipath.conf.5
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH 1/3 multipath-tools: delete obsolete information from multipath.conf.5
repeat_count (rr_min_io, rr_min_io_rq, rr_weight) has been unsupported since kernel 4.6 ( commits 90a4323ccfea and 21136f89d76d ).
And also clean up other deprecated entries.
--- multipath/multipath.conf.5.in | 69 +++-------------------------------- 1 file changed, 6 insertions(+), 63 deletions(-)
multipath/multipath.conf.5.in +6 -63
@@ -6,7 +6,7 @@ .\" Update the date below if you make any significant change. .\" ---------------------------------------------------------------------------- . -.TH MULTIPATH.CONF 5 2025-09-12 Linux +.TH MULTIPATH.CONF 5 2026-05-27 Linux . . .\" ----------------------------------------------------------------------------
@@ -198,9 +198,8 @@ kernel multipath target: .TP 12 .I "round-robin 0" Choose the path for the next bunch of I/O by looping through every path in the -path group, sending \fBthe same number of I/O requests\fR to each path. Some -aspects of behavior can be controlled with the attributes: \fIrr_min_io\fR, -\fIrr_min_io_rq\fR and \fIrr_weight\fR. +path group, sending \fBthe same number of I/O requests\fR to each path. + .TP .I "queue-length 0" (Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on \fBthe lowest
@@ -598,24 +597,12 @@ The default is: \fBmanual\fR . .TP .B rr_min_io -Number of I/O requests to route to a path before switching to the next in the -same path group. This is only for \fIBlock I/O\fR(BIO) based multipath and -only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fB1000\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP .B rr_min_io_rq -Number of I/O requests to route to a path before switching to the next in the -same path group. This is only for \fIRequest\fR based multipath and -only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fB1\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP
@@ -634,16 +621,7 @@ The default is: \fBmax\fR . .TP .B rr_weight -If set to \fIpriorities\fR the multipath configurator will assign path weights -as "path prio * rr_min_io". Possible values are -.I priorities -or -.I uniform . -Only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fBuniform\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP
@@ -821,28 +799,16 @@ The default is: \fB<unset>\fR .TP .B bindings_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/bindings\fR -.RE . . .TP .B wwids_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/wwids\fR -.RE . . .TP .B prkeys_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/prkeys\fR -.RE . . .TP
@@ -1008,10 +974,6 @@ The default is: \fB<unset>\fR .TP .B config_dir (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@CONFIGDIR@\fR -.RE . . .TP
@@ -1324,7 +1286,6 @@ The default is: \fBno\fR .TP .B disable_changed_wwids (Deprecated) This option is not supported anymore, and will be ignored. -.RE . . .TP
@@ -1580,14 +1541,8 @@ section: .TP .B failback .TP -.B rr_weight -.TP .B no_path_retry .TP -.B rr_min_io -.TP -.B rr_min_io_rq -.TP .B flush_on_last_del .TP .B features
@@ -1769,14 +1724,8 @@ section: .TP .B failback .TP -.B rr_weight -.TP .B no_path_retry .TP -.B rr_min_io -.TP -.B rr_min_io_rq -.TP .B fast_io_fail_tmo .TP .B dev_loss_tmo
@@ -1855,14 +1804,8 @@ the values are taken from the \fIdevices\fR or \fIdefaults\fR sections: .TP .B failback .TP -.B rr_weight -.TP .B no_path_retry .TP -.B rr_min_io -.TP -.B rr_min_io_rq -.TP .B flush_on_last_del .TP .B fast_io_fail_tmo
Signature · 1 line
2.54.0
Benjamin Marzinski
maintainerQuoted 28 lines · Xose Vazquez Perez
repeat_count(rr_min_io,rr_min_io_rq,rr_weight) has been unsupported since kernel 4.6 ( commits90a4323ccfeaand21136f89d76d).And also clean up other deprecated entries.
Cc Martin Wilck <[email protected]>Cc Benjamin Marzinski <[email protected]>Cc Christophe Varoqui <[email protected]>Cc DM_DEVEL-ML <[email protected]>Signed-off-by Xose Vazquez Perez <[email protected]>--- multipath/multipath.conf.5.in | 69 +++-------------------------------- 1 file changed, 6 insertions(+), 63 deletions(-)multipath/multipath.conf.5.in +1
-1@@ -6,7 +6,7 @@ .\" Update the date below if you make any significant change. .\" ---------------------------------------------------------------------------- . -.TH MULTIPATH.CONF 5 2025-09-12 Linux +.TH MULTIPATH.CONF 5 2026-05-27 Linux . . .\" ----------------------------------------------------------------------------
multipath/multipath.conf.5.in kernel multipath target: · line 202
Quoted 8 lines
multipath/multipath.conf.5.in +2
-3@@ -198,9 +198,8 @@ kernel multipath target: .TP 12 .I "round-robin 0" Choose the path for the next bunch of I/O by looping through every path in the -path group, sending \fBthe same number of I/O requests\fR to each path. Some -aspects of behavior can be controlled with the attributes: \fIrr_min_io\fR, -\fIrr_min_io_rq\fR and \fIrr_weight\fR. +path group, sending \fBthe same number of I/O requests\fR to each path. +
For the path selectors, we know the number of I/O requests that will be sent, and it's 1. So instead of saying "the next bunch of I/O", we should probably just say "the next I/O request". And we can probably just drop the "sending the same number of I/O requests to each path" part of the round-robin definition.
Quoted 78 lines
multipath/multipath.conf.5.in +3
-36.TP .I "queue-length 0" (Since 2.6.31 kernel) Choose the path for the next bunch of I/O based on \fBthe lowest@@ -598,24 +597,12 @@ The default is: \fBmanual\fR . .TP .B rr_min_io -Number of I/O requests to route to a path before switching to the next in the -same path group. This is only for \fIBlock I/O\fR(BIO) based multipath and -only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fB1000\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP .B rr_min_io_rq -Number of I/O requests to route to a path before switching to the next in the -same path group. This is only for \fIRequest\fR based multipath and -only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fB1\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP@@ -634,16 +621,7 @@ The default is: \fBmax\fR . .TP .B rr_weight -If set to \fIpriorities\fR the multipath configurator will assign path weights -as "path prio * rr_min_io". Possible values are -.I priorities -or -.I uniform . -Only apply to \fIround-robin\fR path_selector. -.RS -.TP -The default is: \fBuniform\fR -.RE +(Deprecated since kernel 4.6) This option is not supported anymore, and will be ignored. . . .TP@@ -821,28 +799,16 @@ The default is: \fB<unset>\fR .TP .B bindings_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/bindings\fR -.RE . . .TP .B wwids_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/wwids\fR -.RE . . .TP .B prkeys_file (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@STATE_DIR@/prkeys\fR -.RE . . .TP
multipath/multipath.conf.5.in The default is: \fB<unset>\fR · line 1014
Quoted 7 lines
multipath/multipath.conf.5.in +0
-4@@ -1008,10 +974,6 @@ The default is: \fB<unset>\fR .TP .B config_dir (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@CONFIGDIR@\fR -.RE
We don't actually specify the location of these files and directories elsewhere in this man page (except for the bindings file), and we do refer to them by these config option names. We should probably replace the references to these option names with the actual file locations, and probably also list the files in a FILES section.
-Ben
Quoted 17 lines · Benjamin Marzinski
multipath/multipath.conf.5.in kernel multipath target: · line 201
Quoted 8 lines · Xose Vazquez Perez
multipath/multipath.conf.5.in +1
-3@@ -198,9 +198,8 @@ kernel multipath target: .TP 12 .I "round-robin 0" Choose the path for the next bunch of I/O by looping through every path in the -path group, sending \fBthe same number of I/O requests\fR to each path. Some -aspects of behavior can be controlled with the attributes: \fIrr_min_io\fR, -\fIrr_min_io_rq\fR and \fIrr_weight\fR. +path group, sending \fBthe same number of I/O requests\fR to each path.For the path selectors, we know the number of I/O requests that will be sent, and it's 1. So instead of saying "the next bunch of I/O", we should probably just say "the next I/O request". And we can probably just drop the "sending the same number of I/O requests to each path" part of the round-robin definition.
Quoted 14 lines
multipath/multipath.conf.5.in The default is: \fB<unset>\fR · line 1014
Quoted 8 lines
multipath/multipath.conf.5.in +0
-4@@ -1008,10 +974,6 @@ The default is: \fB<unset>\fR .TP .B config_dir (Deprecated) This option is not supported anymore, and will be ignored. -.RS -.TP -The compiled-in value is: \fB@CONFIGDIR@\fR -.REWe don't actually specify the location of these files and directories elsewhere in this man page (except for the bindings file), and we do refer to them by these config option names. We should probably replace the references to these option names with the actual file locations, and probably also list the files in a FILES section.
Sounds good. I will address both points and submit the updates in separate patches.
Quoted 4 lines · Xose Vazquez Perez
repeat_count(rr_min_io,rr_min_io_rq,rr_weight) has been unsupported
since kernel 4.6 ( commits90a4323ccfeaand21136f89d76d).
I can't make up my mind on this patch. It is true that most path selectors in the kernel have ignored the repeat_count argument for a long time (historical_service_time still seems to honour it).
But this is multipath-tools. _We_ still have quite a bit of code for handling the minio and weight settings. We should add a hint the the man page that these settings are ignored by modern kernels, but it would be simply wrong to say that _our_ code ignores them while it doesn't.
We can decide to remove this functionality from multipath-tools, which would obviously mean removing it from the man page as well. But if we do, we should apply further cleanups. I suppose that providing the "weightedpath" prioritizer makes no sense if we have no path selector algorithm that takes such weights into account, for example.
I should also note that there have been discussions with some partners about re-introducing parameterized path selectors. This was a topic in the context of Fibre Channel FPIN notifications: FPINs can be used by FC fabric to notify hosts about overloaded paths. With a parameterized path selector, the load on such paths could be decreased by multipathd. temporarily until the situation is normal again. While there has been little progress in this area, I don't consider it cast in stone that the kernel will keep ignoring path selector parameters forever, or IOW, that there won't be new path selectors in the future that do accept path parameters again.
No doubt that the way these parameters are interpreted in different ways ("minio" vs. "weight" vs "repeat_count") and the way this is exposed to end users in the configuration file and in the man page is broken and confusing. But fixing that would be a larger effort.
Regards
Martin
Benjamin Marzinski
maintainerQuoted 33 lines · Martin Wilck
Quoted 4 lines · Xose Vazquez Perez
repeat_count(rr_min_io,rr_min_io_rq,rr_weight) has been unsupported
since kernel 4.6 ( commits90a4323ccfeaand21136f89d76d).I can't make up my mind on this patch. It is true that most path selectors in the kernel have ignored the
repeat_countargument for a long time (historical_service_timestill seems to honour it).But this is multipath-tools. _We_ still have quite a bit of code for handling the minio and weight settings. We should add a hint the the man page that these settings are ignored by modern kernels, but it would be simply wrong to say that _our_ code ignores them while it doesn't.
We can decide to remove this functionality from multipath-tools, which would obviously mean removing it from the man page as well. But if we do, we should apply further cleanups. I suppose that providing the "weightedpath" prioritizer makes no sense if we have no path selector algorithm that takes such weights into account, for example.
I should also note that there have been discussions with some partners about re-introducing parameterized path selectors. This was a topic in the context of Fibre Channel FPIN notifications: FPINs can be used by FC fabric to notify hosts about overloaded paths. With a parameterized path selector, the load on such paths could be decreased by multipathd. temporarily until the situation is normal again. While there has been little progress in this area, I don't consider it cast in stone that the kernel will keep ignoring path selector parameters forever, or IOW, that there won't be new path selectors in the future that do accept path parameters again.
Quoted 4 lines
No doubt that the way these parameters are interpreted in different ways ("minio" vs. "weight" vs "
repeat_count") and the way this is exposed to end users in the configuration file and in the man page is broken and confusing. But fixing that would be a larger effort.
I actually do have a patch set I'm testing that rips out the rr_weight and rr_min_io_rq code completely. It leaves the rr_min_io functionality (on the grounds that we many have a use for it later), but it now defaults to 1 and is deprecated, so it can't be changed. I assume that even if this code gets reused in the future, rr_min_io will remain a bad name for the option.
I feel like the weightedpath priortizer shouldn't be effected by this. It is still useful to manually assign paths to path_groups when combined with group_by_prio.
-Ben
Quoted 3 lines
Regards
Martin
Quoted 53 lines · Benjamin Marzinski
Quoted 46 lines · Martin Wilck
Quoted 4 lines · Xose Vazquez Perez
repeat_count(rr_min_io,rr_min_io_rq,rr_weight) has been unsupported
since kernel 4.6 ( commits90a4323ccfeaand21136f89d76d).I can't make up my mind on this patch. It is true that most path selectors in the kernel have ignored the
repeat_countargument for a long time (historical_service_timestill seems to honour it).But this is multipath-tools. _We_ still have quite a bit of code for
handling the minio and weight settings. We should add a hint the the
man page that these settings are ignored by modern kernels, but it would be simply wrong to say that _our_ code ignores them while it doesn't.We can decide to remove this functionality from multipath-tools, which
would obviously mean removing it from the man page as well. But if we
do, we should apply further cleanups. I suppose that providing the "weightedpath" prioritizer makes no sense if we have no path selector
algorithm that takes such weights into account, for example.I should also note that there have been discussions with some partners
about re-introducing parameterized path selectors. This was a topic in
the context of Fibre Channel FPIN notifications: FPINs can be used by
FC fabric to notify hosts about overloaded paths. With a parameterized
path selector, the load on such paths could be decreased by multipathd.
temporarily until the situation is normal again. While there has been
little progress in this area, I don't consider it cast in stone that
the kernel will keep ignoring path selector parameters forever, or IOW,
that there won't be new path selectors in the future that do accept path parameters again.Quoted 5 lines
No doubt that the way these parameters are interpreted in different ways ("minio" vs. "weight" vs "
repeat_count") and the way this is exposed to end users in the configuration file and in the man page is
broken and confusing. But fixing that would be a larger effort.
Quoted 9 lines
I actually do have a patch set I'm testing that rips out the
rr_weight
andrr_min_io_rqcode completely. It leaves therr_min_iofunctionality
(on the grounds that we many have a use for it later), but it now defaults to 1 and is deprecated, so it can't be changed. I assume that
even if this code gets reused in the future,rr_min_iowill remain a bad name for the option.
That would be a welcome addition to Xose's set, then.
Quoted 5 lines
I feel like the weightedpath priortizer shouldn't be effected by this.
It is still useful to manually assign paths topath_groupswhen combined
withgroup_by_prio.
I see that it's possible. Assigning weights only as sort of a sort key for path grouping appears somewhat non-obvious and over-complicated to me. But fair enough, some people may use it this way indeed.
Martin
PATCH 2/3 multipath-tools: remove explicit width from .TP macros in multipath.conf.5
In reply to a message not in the archiveThis allows man/groff to calculate the width automatically, preventing excessive whitespace and improving readability on various terminal sizes.
--- multipath/multipath.conf.5.in | 56 +++++++++++++++++------------------ 1 file changed, 28 insertions(+), 28 deletions(-)
multipath/multipath.conf.5.in +28 -28
@@ -103,7 +103,7 @@ matches, standard regular expression syntax using the special characters "^" and .LP . The following \fIsection\fP keywords are recognized: -.TP 17 +.TP .B defaults This section defines default values for attributes which are used whenever no values are given in the appropriate device or multipath
@@ -142,7 +142,7 @@ device-specific settings for all devices. The \fIdefaults\fR section recognizes the following keywords: . . -.TP 17 +.TP .B verbosity Default verbosity. Higher values increase the verbosity level. Valid levels are between 0 and 6.
@@ -195,7 +195,7 @@ The default is: \fBno\fR The default path selector algorithm to use; they are offered by the kernel multipath target: .RS -.TP 12 +.TP .I "round-robin 0" Choose the path for the next bunch of I/O by looping through every path in the path group, sending \fBthe same number of I/O requests\fR to each path.
@@ -223,7 +223,7 @@ The default is: \fBservice-time 0\fR (Hardware-dependent) The default path grouping policy to apply to unspecified multipaths. Possible values are: .RS -.TP 12 +.TP .I failover One path per priority group. .TP
@@ -333,7 +333,7 @@ of this path. Higher number have a higher priority. \fI"none"\fR is a valid value. Currently the following path priority routines are implemented: .RS -.TP 12 +.TP .I const Return a constant priority of \fI1\fR. .TP
@@ -408,12 +408,12 @@ NetAPP E/EF Series, where it is \fBalua\fR). If \fBdetect_prio\fR is Arguments to pass to to the prio function. This only applies to certain prioritizers: .RS -.TP 12 +.TP .I weighted Needs a value of the form \fI"<hbtl|devname|serial|wwn> <regex1> <prio1> <regex2> <prio2> ..."\fR .RS -.TP 8 +.TP .I hbtl Regex can be of SCSI H:B:T:L format. For example: 1:0:.:. , *:0:0:. .TP
@@ -430,11 +430,11 @@ Regex can be of the form \fI"host_wwnn:host_wwpn:target_wwnn:target_wwpn"\fR these values can be looked up through sysfs or by running \fImultipathd show paths format "%N:%R:%n:%r"\fR. For example: 0x200100e08ba0aea0:0x210100e08ba0aea0:.*:.* , .*:.*:iqn.2009-10.com.redhat.msp.lab.ask-06:.* .RE -.TP 12 +.TP .I path_latency Needs a value of the form "io_num=\fI<20>\fR base_num=\fI<10>\fR" .RS -.TP 8 +.TP .I io_num The number of read IOs sent to the current path continuously, used to calculate the average path latency. Valid Values: Integer, [20, 200].
@@ -445,7 +445,7 @@ Double-precision floating-point, [1.1, 10]. And Max average latency value is 100 For example: If base_num=10, the paths will be grouped in priority groups with path latency <=1us, (1us, 10us], (10us, 100us], (100us, 1ms], (1ms, 10ms], (10ms, 100ms], (100ms, 1s], (1s, 10s], (10s, 100s], >100s. .RE -.TP 12 +.TP .I alua If \fIexclusive_pref_bit\fR is set, paths with the \fIpreferred path\fR bit set will always be in their own path group.
@@ -456,17 +456,17 @@ set will always be in their own path group. .TP .I datacore .RS -.TP 8 +.TP .I preferredsds (Mandatory) The preferred "SDS name". .TP .I timeout (Optional) The timeout for the INQUIRY, in ms. .RE -.TP 12 +.TP .I iet .RS -.TP 8 +.TP .I preferredip=... (Mandatory) Th preferred IP address, in dotted decimal notation, for iSCSI targets. .RE
@@ -481,7 +481,7 @@ Specify any device-mapper features to be used. Syntax is \fInum list\fR where \fInum\fR is the number, between 0 and 8, of features in \fIlist\fR. Possible values for the feature list are: .RS -.TP 12 +.TP .I queue_if_no_path (Deprecated, superseded by \fIno_path_retry\fR) Queue I/O if no path is active. Identical to the \fIno_path_retry\fR with \fIqueue\fR value. If both this
@@ -520,7 +520,7 @@ to respond. The asynchronous checkers (\fItur\fR and \fIdirectio\fR) will not pause multipathd. Instead, multipathd will check for a response once per second, until \fIchecker_timeout\fR seconds have elapsed. Possible values are: .RS -.TP 12 +.TP .I readsector0 (Deprecated) Read the first sector of the device. This checker is being deprecated, please use \fItur\fR or \fIdirectio\fR instead.
@@ -574,7 +574,7 @@ Tell multipathd how to manage path group failback. To select \fIimmediate\fR or a \fIvalue\fR, it's mandatory that the device has support for a working prioritizer. .RS -.TP 12 +.TP .I immediate Immediately failback to the highest priority pathgroup that contains active paths.
@@ -628,7 +628,7 @@ The default is: \fBmax\fR .B no_path_retry Specify what to do when all paths are down. Possible values are: .RS -.TP 12 +.TP .I value > 0 Number of retries until disable I/O queueing. .TP
@@ -1154,7 +1154,7 @@ blocked from further processing by higher layers - such as LVM - if and only if it\'s considered a valid multipath device path), and b) when multipathd detects a new device. The following values are possible: .RS -.TP 10 +.TP .I strict Both multipath and multipathd treat only such devices as multipath devices which have been part of a multipath map previously, and which are therefore
@@ -1421,7 +1421,7 @@ by multipath-tools. . The following keywords are recognized in both sections. The defaults are empty unless explicitly stated. -.TP 17 +.TP .B devnode Regular expression matching the device nodes to be excluded/included. .RS
@@ -1511,7 +1511,7 @@ from later entries take precedence. . . The \fImultipath\fR subsection recognizes the following attributes: -.TP 17 +.TP .B wwid (Mandatory) World Wide Identifier. Detected multipath maps are matched against this attribute. Note that, unlike the \fIwwid\fR attribute in the \fIblacklist\fR section,
@@ -1530,7 +1530,7 @@ section: .sp 1 .PD .1v .RS -.TP 18 +.TP .B path_grouping_policy .TP .B path_selector
@@ -1587,7 +1587,7 @@ section: .SH "devices section" .\" ---------------------------------------------------------------------------- . -.TP 4 +.TP .B Important: The built-in hardware device table of .I multipath-tools
@@ -1623,7 +1623,7 @@ for all devices in the system. .LP . The \fIdevice\fR subsection recognizes the following attributes: -.TP 17 +.TP .B vendor (Mandatory) Regular expression to match the vendor name. .RS
@@ -1666,7 +1666,7 @@ and \fImultipathd show paths format\fR commands. Currently only the The hardware handler to use for this device type. The following hardware handler are implemented: .RS -.TP 12 +.TP .I 1 emc (Hardware-dependent) Hardware handler for DGC class arrays as CLARiiON CX/AX and EMC VNX families
@@ -1707,7 +1707,7 @@ section: .sp 1 .PD .1v .RS -.TP 18 +.TP .B path_grouping_policy .TP .B uid_attribute
@@ -1785,7 +1785,7 @@ the values are taken from the \fIdevices\fR or \fIdefaults\fR sections: .sp 1 .PD .1v .RS -.TP 18 +.TP .B path_grouping_policy .TP .B uid_attribute
@@ -1899,7 +1899,7 @@ which paths belong to the same device. Each path presenting the same WWID is assumed to point to the same device. .LP The WWID is generated by four methods (in the order of preference): -.TP 17 +.TP .B uid_attrs The WWID is derived from udev attributes by matching the device node name; cf \fIuid_attrs\fR above.
@@ -1939,7 +1939,7 @@ pathgroups will not be used until all other pathgroups have been tried. At the time when the path would normally be reinstated, it will be returned to its normal pathgroup. The logic of determining \(dqshaky\(dq condition, as well as the logic when to reinstate, differs between the three methods. -.TP 8 +.TP .B \(dqdelay_checks\(dq failure tracking (Deprecated) This method is \fBdeprecated\fR and mapped to the \(dqsan_path_err\(dq method. See the \fIdelay_watch_checks\fR and \fIdelay_wait_checks\fR options above
Signature · 1 line
2.54.0
Re: [PATCH 2/3] multipath-tools: remove explicit width from .TP macros in multipath.conf.5
Quoted 8 lines · Xose Vazquez Perez
This allows man/groff to calculate the width automatically, preventing excessive whitespace and improving readability on various terminal sizes.
Cc Martin Wilck <[email protected]>Cc Benjamin Marzinski <[email protected]>Cc Christophe Varoqui <[email protected]>Cc DM_DEVEL-ML <[email protected]>Signed-off-by Xose Vazquez Perez <[email protected]>
PATCH 3/3 multipath-tools: remove explicit widths from macros in the remaining man pages
In reply to a message not in the archiveThis allows man/groff to calculate the width automatically, preventing excessive whitespace and improving readability on various terminal sizes.
--- libmpathpersist/mpath_persistent_reserve_in.3 | 4 ++-- libmpathpersist/mpath_persistent_reserve_out.3 | 4 ++-- mpathpersist/mpathpersist.8.in | 2 +- multipath/multipath.8.in | 6 +++--- multipath/multipath.conf.5.in | 10 +++++----- multipathd/multipathd.8.in | 9 ++++----- 6 files changed, 17 insertions(+), 18 deletions(-)
libmpathpersist/mpath_persistent_reserve_in.3 +2 -2
@@ -35,7 +35,7 @@ the DM device and gets the response. .TP .B Parameters: .RS -.TP 12 +.TP .I fd The file descriptor of a multipath device. Input argument. .TP
@@ -57,7 +57,7 @@ Set verbosity level. Input argument. value:[0-3]. 0->Errors, 1->Warnings, 2->Inf .SH RETURNS .\" ---------------------------------------------------------------------------- . -.TP 12 +.TP .B MPATH_PR_SUCCESS If PR command successful. .TP
libmpathpersist/mpath_persistent_reserve_out.3 +2 -2
@@ -35,7 +35,7 @@ the DM device and gets the response. .TP .B Parameters: .RS -.TP 12 +.TP .I fd The file descriptor of a multipath device. Input argument. .TP
@@ -74,7 +74,7 @@ Set verbosity level. Input argument. value: 0 to 3. 0->Errors, 1->Warnings, 2->I .SH RETURNS .\" ---------------------------------------------------------------------------- . -.TP 12 +.TP .B MPATH_PR_SUCCESS If PR command successful else returns any one of the status mentioned below. .TP
mpathpersist/mpathpersist.8.in +1 -1
@@ -50,7 +50,7 @@ various options. .BI \-verbose|\-v " level" Verbosity: .RS -.TP 5 +.TP .I 0 Critical messages. .TP
multipath/multipath.8.in +3 -3
@@ -100,7 +100,7 @@ The \fBdevice\fR argument restricts \fBmultipath\fR's operation to devices match expression. The argument may refer either to a multipath map or to its components ("paths"). The expression may be in one of the following formats: . -.TP 1.4i +.TP .B device node file name of a device node, e.g. \fI/dev/dm-10\fR or \fI/dev/sda\fR. If the node refers to an existing device mapper device representing a multipath map, this selects
@@ -195,8 +195,8 @@ creating \fI@CONFIGFILE@\fR. .BI \-v " level" Verbosity of information printed to stdout in default and "list" operation modes. The default level is \fI-v 2\fR. -.RS 1.2i -.TP 1.2i +.RS +.TP .I 0 Nothing is printed. .TP
multipath/multipath.conf.5.in +5 -5
@@ -1527,7 +1527,7 @@ the same WWID in the \fIbindings_file\fR. The following attributes are optional; if not set the default values are taken from the \fIoverrides\fR, \fIdevices\fR, or \fIdefaults\fR section: -.sp 1 +.sp .PD .1v .RS .TP
@@ -1704,7 +1704,7 @@ has no effect. The following attributes are optional; if not set the default values are taken from the \fIdefaults\fR section: -.sp 1 +.sp .PD .1v .RS .TP
@@ -1782,7 +1782,7 @@ section: . The overrides section recognizes the following optional attributes; if not set the values are taken from the \fIdevices\fR or \fIdefaults\fR sections: -.sp 1 +.sp .PD .1v .RS .TP
@@ -1878,7 +1878,7 @@ exactly. The protocol that a path is using can be viewed by running .LP The following attributes are optional; if not set, the default values are taken from the \fIoverrides\fR, \fIdevices\fR, or \fIdefaults\fR section: -.sp 1 +.sp .PD .1v .RS .TP
@@ -1969,7 +1969,7 @@ 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 +.RS .LP This algorithm is superseded by the \(dqmarginal_path\(dq failure tracking, but remains supported for backward compatibility.
multipathd/multipathd.8.in +4 -5
@@ -416,7 +416,7 @@ appropriate device information. The following wildcards are supported. .TP .B Multipath format wildcards .RS -.TP 12 +.TP .B %n The device name. .TP
@@ -521,7 +521,7 @@ the configured one). .TP .B Path format wildcards .RS -.TP 12 +.TP .B %w The device WWID (uuid). .TP
@@ -548,7 +548,7 @@ sysfs states, it shows "running". .B %T The multipathd path checker state of the device. The possible states are: .RS -.TP 12 +.TP .I ready The device is ready to handle IO. .TP
@@ -693,8 +693,7 @@ Overrides the \fImax_fds\fR configuration setting. . .BR multipathc (8), .BR multipath (8), -.BR kpartx (8) -.RE +.BR kpartx (8), .BR sd_notify (3), .BR systemd.service (5). .
Signature · 1 line
2.54.0
Re: [PATCH 3/3] multipath-tools: remove explicit widths from macros in the remaining man pages
Quoted 8 lines · Xose Vazquez Perez
This allows man/groff to calculate the width automatically, preventing excessive whitespace and improving readability on various terminal sizes.
Cc Martin Wilck <[email protected]>Cc Benjamin Marzinski <[email protected]>Cc Christophe Varoqui <[email protected]>Cc DM_DEVEL-ML <[email protected]>Signed-off-by Xose Vazquez Perez <[email protected]>