From: hch@infradead.org (Christoph Hellwig)
Subject: Duplicate subnqn of NVMe SSD Controllers
Date: Sat, 27 Oct 2018 01:26:23 -0700 [thread overview]
Message-ID: <20181027082623.GA25033@infradead.org> (raw)
In-Reply-To: <5m6gor-7xj0dn5dtb12x1b8f3-xfsypw-s3pjnd-oq8eyy-82l7b1-qdnqdci1wm87jp0w3aj5wymq-xt9rda-x787pwq8q8mz-118hyj7ztvz0flkog2-9es5q86pqysjjks19b-ps9rfn-a0r0vp7260ev.1540625692098@email.android.com>
On Sat, Oct 27, 2018@03:34:52PM +0800, zhitaoli1201@163.com wrote:
> Hello, everyone,
>
>
> I am Zhitao Li, interested in Linux kernel and?SSDs.
>
> I am writing nvme device drivers based on my Open-channel SSDs. However, when two SSDs are connected to motherboard and Linux(4.17) boots, following warning information will be printed in the booting process:
>
>
> "nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2014.08.org.nvmexpress:1ded1dedAA....)"
This means your devices have a duplicate serial (and model, but that is
expected) number, which means they are buggy in a way that can have
data integrity consequences. Please talk to the vendor so that the
firmware will provide a proper unique serial number.
prev parent reply other threads:[~2018-10-27 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 7:34 Duplicate subnqn of NVMe SSD Controllers zhitaoli1201
2018-10-27 8:26 ` Christoph Hellwig [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=20181027082623.GA25033@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox