From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
dm-devel@lists.linux.dev, Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH] multipath.conf.in: Update path_checker and force_sync documentation
Date: Mon, 6 Jul 2026 20:08:23 -0400 [thread overview]
Message-ID: <akxDd23q6CnxTOqB@redhat.com> (raw)
In-Reply-To: <20260706135049.724071-1-mwilck@suse.com>
On Mon, Jul 06, 2026 at 03:50:49PM +0200, Martin Wilck wrote:
> Document the fact that all path checkers are now asynchronous by default.
>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> multipath/multipath.conf.5.in | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/multipath/multipath.conf.5.in b/multipath/multipath.conf.5.in
> index e6b4fc0..2ea78fc 100644
> --- a/multipath/multipath.conf.5.in
> +++ b/multipath/multipath.conf.5.in
> @@ -504,12 +504,11 @@ The default is: \fB0\fR
> .
> .TP
> .B path_checker
> -The default method used to determine the path's state. The synchronous
> -checkers (all except \fItur\fR and \fIdirectio\fR) will cause multipathd to
> -pause most activity, waiting up to \fIchecker_timeout\fR seconds for the path
> -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:
> +The default method used to determine the path's state. Since multipath-tools
> +0.15.0, all path checkers run in asynchronous mode by default, so that
> +unresponsive devices don't pause multipathd. Use the \fIforce_sync\fR parameter
> +to enforce synchronous path checking instead.
> +Possible values are:
> .RS
> .TP
> .I readsector0
> @@ -905,7 +904,8 @@ The default is: \fByes\fR
> If set to
> .I yes
> , multipathd will call the path checkers in sync mode only. This means that
> -only one checker will run at a time. This is useful in the case where many
> +only one checker will run at a time, and that multipathd may pause operating
> +while it is waiting for a device to respond. This is useful in the case where many
> multipathd checkers running in parallel causes significant CPU pressure.
> .RS
> .TP
> --
> 2.54.0
prev parent reply other threads:[~2026-07-07 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 13:50 [PATCH] multipath.conf.in: Update path_checker and force_sync documentation Martin Wilck
2026-07-07 0:08 ` Benjamin Marzinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=akxDd23q6CnxTOqB@redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=martin.wilck@suse.com \
--cc=mwilck@suse.com \
--cc=xose.vazquez@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.