nvme_free_ns_head: ida_remove called for id=1 which is not allocated

[Alex G.]

On 04/03/2018 04:07 PM, Keith Busch wrote:
> On Tue, Apr 03, 2018 at 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.