From: "hch@lst.de" <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>, "hch@lst.de" <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Jeffrey Lien <Jeff.Lien@wdc.com>
Subject: Re: Buffer I/O Errors from Zoned NVME devices
Date: Mon, 1 Feb 2021 19:02:57 +0100 [thread overview]
Message-ID: <20210201180257.GA14971@lst.de> (raw)
In-Reply-To: <20210201175306.GA2127465@dhcp-10-100-145-180.wdc.com>
On Mon, Feb 01, 2021 at 09:53:06AM -0800, Keith Busch wrote:
> On Mon, Feb 01, 2021 at 02:36:12PM +0000, Jeffrey Lien wrote:
> > Christoph, Keith
> > We're seeing a lot of these Buffer I/O errors with our zoned nvme devices. One of the FW developers looked into it and had the following explanation:
> > All these Reads are from the kernel during enumeration and for LBAs that are in last zone's hole hence expected to return boundary error which is getting logged by kernel.
> >
> > [65281.936988] Buffer I/O error on dev nvme1n2, logical block 3800039296, async page read
> > [65281.937165] blk_update_request: I/O error, dev nvme1n2, sector 3800039297 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> > [65281.937166] Buffer I/O error on dev nvme1n2, logical block 3800039297, async page read
> > [65281.937335] blk_update_request: I/O error, dev nvme1n2, sector 3800039298 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> > [65281.937336] Buffer I/O error on dev nvme1n2, logical block 3800039298, async page read
> > [65281.937498] blk_update_request: I/O error, dev nvme1n2, sector 3800039299 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> >
> > Are you aware of this issue and if so, do you have any recommendations on how to avoid or resolve?
>
> Is this from the partition scanning? We don't partition zoned devices,
> so I think we can skip it. Does the following resolve the issue?
We already have special zoned device handling in the partitioning code.
But NVMe should make sure to never span a zone boundary as we set the
chunk size to avoid that.
What kernel version is this? Is CONFIG_BLK_DEV_ZONED enabled?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-01 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 14:36 Buffer I/O Errors from Zoned NVME devices Jeffrey Lien
2021-02-01 17:53 ` Keith Busch
2021-02-01 18:02 ` hch [this message]
2021-02-01 21:04 ` Damien Le Moal
2021-02-02 15:06 ` Jeffrey Lien
2021-02-02 15:22 ` Keith Busch
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=20210201180257.GA14971@lst.de \
--to=hch@lst.de \
--cc=Damien.LeMoal@wdc.com \
--cc=Jeff.Lien@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.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.