From: keith.busch@linux.intel.com (Keith Busch)
Subject: Bug report: critical medium error during 8k local nvme write
Date: Tue, 5 Jun 2018 10:20:53 -0600 [thread overview]
Message-ID: <20180605162053.GC16899@localhost.localdomain> (raw)
In-Reply-To: <93935ee4-52eb-a514-1b46-21c0f3b6e31d@mellanox.com>
On Tue, May 29, 2018@04:08:08PM +0300, Max Gurtovoy wrote:
> hi Keith,
> I want to report on a bug I've seen in my local nvme drive configured to run
> with metadata format using:
I think you got this one fixed in your patch "nvme: Fix extended data
LBA supported setting".
next prev parent reply other threads:[~2018-06-05 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 13:08 Bug report: critical medium error during 8k local nvme write Max Gurtovoy
2018-06-05 16:20 ` Keith Busch [this message]
2018-06-05 20:54 ` Max Gurtovoy
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=20180605162053.GC16899@localhost.localdomain \
--to=keith.busch@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox