From: keith.busch@intel.com (Keith Busch)
Subject: nvme_free_ns_head: ida_remove called for id=1 which is not allocated
Date: Wed, 4 Apr 2018 09:56:09 -0600 [thread overview]
Message-ID: <20180404155609.GF4485@localhost.localdomain> (raw)
In-Reply-To: <7302eff4-cf8b-e479-112b-c9a366b598dc@gmail.com>
On Wed, Apr 04, 2018@10:51:33AM -0500, Alex G. wrote:
> On 04/03/2018 04:07 PM, Keith Busch wrote:
> > On Tue, Apr 03, 2018@12:46:34PM -0500, Alex G. wrote:
> >> I noticed a new and interesting error. While it's ominous, it doesn't
> >> seem to cause any ill side-effects. This is reproduced with
> >> firmware-first error handling, so I'm not sure if it's even an issue of
> >> concern to nvme_core. Log files attached
> >
> > Does this reproduce if you're not using CONFIG_NVME_MULTIPATH?
>
> I'm not seeing it with 'CONFIG_NVME_MULTIPATH is not set' after running
> this overnight.
Thanks. There are different code paths the two modes may take. I don't
see anything obviously wrong yet, so just wanted to narrow the scope of
the search down.
prev parent reply other threads:[~2018-04-04 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 17:46 nvme_free_ns_head: ida_remove called for id=1 which is not allocated Alex G.
2018-04-03 21:07 ` Keith Busch
2018-04-04 15:51 ` Alex G.
2018-04-04 15:56 ` Keith Busch [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=20180404155609.GF4485@localhost.localdomain \
--to=keith.busch@intel.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.