Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: NVMeoF: multipath stuck after bringing one ethernet port down
Date: Mon, 5 Jun 2017 10:40:37 +0200	[thread overview]
Message-ID: <20170605084037.GB22677@lst.de> (raw)
In-Reply-To: <459af627-3918-768e-c35f-3f99768b82cb@grimberg.me>

On Tue, May 30, 2017@05:17:40PM +0300, Sagi Grimberg wrote:
> [PATCH] nvme-rdma: fast fail incoming requests while we reconnect
>
> When we encounter an transport/controller errors, error recovery
> kicks in which performs:
> 1. stops io/admin queues
> 2. moves transport queues out of LIVE state
> 3. fast fail pending io
> 4. schedule periodic reconnects.
>
> But we also need to fast fail incoming IO taht enters after we
> already scheduled. Given that our queue is not LIVE anymore, simply
> restart the request queues to fail in .queue_rq

But we shouldn't _fail_ I/O just because we're reconnecting, we
need to be able to retry it once reconnected.

> +                   cmd->fabrics.fctype != nvme_fabrics_type_connect) {
> +                       if (queue->ctrl->ctrl->state == 
> NVME_CTRL_RECONNECTING)
> +                               return -EIO;
> +                       else
> +                               return -EAGAIN;
> +               }

So this looks somewhat bogus to me, while the rest looks ok.

  parent reply	other threads:[~2017-06-05  8:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 16:08 NVMeoF: multipath stuck after bringing one ethernet port down Alex Turin
2017-05-17 17:28 ` Sagi Grimberg
2017-05-18  5:52   ` shahar.salzman
2017-05-23 17:31     ` shahar.salzman
2017-05-25 11:06       ` shahar.salzman
2017-05-25 12:27         ` shahar.salzman
2017-05-25 13:08           ` shahar.salzman
2017-05-30 12:14           ` Sagi Grimberg
2017-05-30 12:11         ` Sagi Grimberg
2017-05-30 12:05       ` Sagi Grimberg
2017-05-30 13:37         ` Max Gurtovoy
2017-05-30 14:17           ` Sagi Grimberg
2017-06-05  7:11             ` shahar.salzman
2017-06-05  8:14               ` Sagi Grimberg
2017-06-05  8:40             ` Christoph Hellwig [this message]
2017-06-05  8:53               ` Sagi Grimberg
2017-06-05 15:07                 ` Christoph Hellwig
2017-06-05 17:23                   ` Sagi Grimberg

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=20170605084037.GB22677@lst.de \
    --to=hch@lst.de \
    /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