qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-block@nongnu.org, hreitz@redhat.com, bmarzins@redhat.com,
	pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] file-posix: Probe paths and retry SG_IO on potential path errors
Date: Thu, 22 May 2025 16:57:10 +0200	[thread overview]
Message-ID: <aC87RvpJ9O-4jmMM@redhat.com> (raw)
In-Reply-To: <20250522144607.GA258433@fedora>

[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]

Am 22.05.2025 um 16:46 hat Stefan Hajnoczi geschrieben:
> On Thu, May 22, 2025 at 03:08:03PM +0200, Kevin Wolf wrote:
> > When scsi-block is used on a host multipath device, it runs into the
> > problem that the kernel dm-mpath doesn't know anything about SCSI or
> > SG_IO and therefore can't decide if a SG_IO request returned an error
> > and needs to be retried on a different path. Instead of getting working
> > failover, an error is returned to scsi-block and handled according to
> > the configured error policy. Obviously, this is not what users want,
> > they want working failover.
> > 
> > QEMU can parse the SG_IO result and determine whether this could have
> > been a path error, but just retrying the same request could just send it
> > to the same failing path again and result in the same error.
> > 
> > With a kernel that supports the DM_MPATH_PROBE_PATHS ioctl on dm-mpath
> > block devices (queued in the device mapper tree for Linux 6.16), we can
> > tell the kernel to probe all paths and tell us if any usable paths
> > remained. If so, we can now retry the SG_IO ioctl and expect it to be
> > sent to a working path.
> > 
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > v2:
> > - Add a comment to explain retry scenarios [Stefan]
> > - Handle -EAGAIN returned for suspended devices [Ben]

> >  #if defined(__linux__)
> > +#if defined(DM_MPATH_PROBE_PATHS)
> > +static bool sgio_path_error(int ret, sg_io_hdr_t *io_hdr)
> > +{
> > +    if (ret < 0) {
> > +        switch (ret) {
> > +        case -ENODEV:
> > +            return true;
> > +        case -EAGAIN:
> > +            /*
> > +             * The device is probably suspended. This happens while the dm table
> > +             * is reloaded, e.g. because a path is added or removed. This is an
> > +             * operation that should complete within 1ms, so just wait a bit and
> > +             * retry.
> > +             *
> > +             * If the device was suspended for another reason, we'll wait and
> > +             * retry SG_IO_MAX_RETRIES times. This is a tolerable delay before
> > +             * we return an error and potentially stop the VM.
> > +             */
> > +            qemu_co_sleep_ns(QEMU_CLOCK_REALTIME, 1000000);
> 
> sgio_path_error() is missing coroutine_fn.
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

Thanks, good catch. I already applied the patch and fixed it up to make
sure that I won't forget.

Kevin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-05-22 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 13:08 [PATCH v2] file-posix: Probe paths and retry SG_IO on potential path errors Kevin Wolf
2025-05-22 14:46 ` Stefan Hajnoczi
2025-05-22 14:57   ` Kevin Wolf [this message]
2025-05-22 15:13 ` Hanna Czenczek

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=aC87RvpJ9O-4jmMM@redhat.com \
    --to=kwolf@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).