linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Eduard Hasenleithner <eduard@hasenleithner.at>
To: Dakshaja Uppalapati <dakshaja@chelsio.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"kbusch@kernel.org" <kbusch@kernel.org>
Cc: Potnuri Bharat Teja <bharat@chelsio.com>,
	Nirranjan Kirubaharan <nirranjan@chelsio.com>
Subject: Re: nvme blk_update_request IO error observed on formatting device with kernels 5.5-rc1 and above.
Date: Fri, 27 Dec 2019 16:03:57 +0100	[thread overview]
Message-ID: <0b33acdb-2b8c-2a06-3c6d-b978f9a760ad@hasenleithner.at> (raw)
In-Reply-To: <CH2PR12MB40053A64681EFA3E6F63FDFBDD2A0@CH2PR12MB4005.namprd12.prod.outlook.com>

On 27.12.19 15:08, Dakshaja Uppalapati wrote:
> I am trying to setup and run NVMF with tot linux kernel installed(5.5.0-rc3) on
> both target and host. Attached is the target configuration using ramdisk device.

> The following error is seen in dmesg:
> [  219.507989] blk_update_request: I/O error, dev nvme0c0n1, sector 0 op 0x3:(DISCARD) flags 0x4000800 phys_seg 1 prio class 0

> Please let me know if any info is needed further.

How big is the ramdisk?
Are there further error messages in the kernel log?
My current speculation is that it might fail in blk_cloned_rq_check_limits,
but then there should be an additional error message,
 e.g. "blk_cloned_rq_check_limits: over max size limit".

Eduard




_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2019-12-27 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 14:08 nvme blk_update_request IO error observed on formatting device with kernels 5.5-rc1 and above Dakshaja Uppalapati
2019-12-27 15:03 ` Eduard Hasenleithner [this message]
2019-12-28  9:01   ` Sagi Grimberg
2019-12-30 10:52     ` Dakshaja Uppalapati
2020-01-24  8:51       ` Dakshaja Uppalapati
2020-01-24 17:40         ` Sagi Grimberg

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=0b33acdb-2b8c-2a06-3c6d-b978f9a760ad@hasenleithner.at \
    --to=eduard@hasenleithner.at \
    --cc=bharat@chelsio.com \
    --cc=dakshaja@chelsio.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nirranjan@chelsio.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;
as well as URLs for NNTP newsgroup(s).