From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH] nvme-cli: Revert stop-on-failure with connect-all
Date: Tue, 9 Apr 2019 15:04:49 -0600 [thread overview]
Message-ID: <20190409210448.GA3272@localhost.localdomain> (raw)
In-Reply-To: <20190409205154.15197-1-jsmart2021@gmail.com>
On Tue, Apr 09, 2019@01:51:54PM -0700, James Smart wrote:
> The patch that added special treatment for EALREADY connect failures
> also changed the behavior on what happens if a discovery log contains
> an entry that is not connectable by the system or host port. If it
> encounters a log entry that can't be connected to, it will not attempt
> to connect to any log entries beyond it. This can leave lots of devices
> unconnected to.
>
> Revert the stop-on-failure introduced by the previous patch.
>
> Specifically, this failed for me on an FC array that had a discovery log
> entry for a port that was not visible via zoning for the initiator
> port being used.
Patch applied. I just tagged a release earlier this week, so let me know
if this is urgent enough to warrant a new tag.
next prev parent reply other threads:[~2019-04-09 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 20:51 [PATCH] nvme-cli: Revert stop-on-failure with connect-all James Smart
2019-04-09 21:04 ` Keith Busch [this message]
2019-04-09 21:25 ` James Smart
2019-04-09 21:38 ` Keith Busch
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=20190409210448.GA3272@localhost.localdomain \
--to=kbusch@kernel.org \
/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).