From: hch@infradead.org (Christoph Hellwig)
Subject: Two M.2 NVMe drives with same NQN, one gets removed
Date: Mon, 26 Nov 2018 23:54:27 -0800 [thread overview]
Message-ID: <20181127075426.GA4173@infradead.org> (raw)
In-Reply-To: <20181126153110.GM26707@localhost.localdomain>
On Mon, Nov 26, 2018@08:31:11AM -0700, Keith Busch wrote:
> According to the resolution discussion here:
>
> https://downloadcenter.intel.com/download/28320/Known-Issue-Intel-SSD-760p-Pro-7600p-Series-SubNQN-Conflict-on-Linux
>
> "
> If you purchased your Intel? SSD from an OEM, your firmware version may
> have a different naming. Contact your local OEM representative for
> latest firmware revisions.
> "
>
> Sounds like Lenovo will need to merge the Intel update into their
> specific firmware if they haven't already done so.
OEMs are notoriously bad in picking up firmware fixes. If the problems
with this drive persist we should probably add a quick that ignores the
drive provided NQN and build up one from based on the legacy
model/serial number algorithm instead.
next prev parent reply other threads:[~2018-11-27 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 13:38 Two M.2 NVMe drives with same NQN, one gets removed James Dingwall
2018-11-26 15:31 ` Keith Busch
2018-11-27 7:54 ` Christoph Hellwig [this message]
2018-11-27 10:25 ` James Dingwall
2018-11-27 15:01 ` Keith Busch
2018-11-30 11:50 ` James Dingwall
-- strict thread matches above, loose matches on Subject: below --
2018-11-17 0:17 John Van Bockel
2018-11-17 1:33 ` Keith Busch
2018-11-18 19:08 ` John Van Bockel
[not found] ` <CAGmwwfc=g+4h12qMBvRVJoE66Z70kzzfkabjyxLC=d7LZp627A@mail.gmail.com>
2018-11-19 17:00 ` Keith Busch
2018-11-21 21:19 ` John Van Bockel
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=20181127075426.GA4173@infradead.org \
--to=hch@infradead.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 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.