All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Xiong <wenxiong@linux.ibm.com>
To: linux-nvme@lists.infradead.org
Cc: Wenxiong <wenxiong@us.ibm.com>
Subject: Saw I/O errors while delete/create/attach a namespace on nvme device.
Date: Mon, 06 Nov 2023 22:10:33 -0600	[thread overview]
Message-ID: <ee222a8c6574d754d7e6355591e1a06a@linux.ibm.com> (raw)

Hi All,

I am working on new nvme device and found this: nguid is changed while 
delete/create/attach a namespace, we saw some error messages in linux 
log.

Should we see these errors messages since recreating namespaces or are 
there some issues in error path?

# dmesg
[10524.330156] nvme nvme0: rescanning namespaces.
[10524.338810] nvme nvme0: identifiers changed for nsid 1
[10524.343448] block nvme0n1: no usable path - requeuing I/O
[10524.480468] block nvme0n1: no available path - failing I/O
[10524.480497] block nvme0n1: no available path - failing I/O
[10524.480501] Buffer I/O error on dev nvme0n1, logical block 781402912, 
async page read
[10524.480508] block nvme0n1: no available path - failing I/O
[10524.480510] Buffer I/O error on dev nvme0n1, logical block 781402913, 
async page read
[10524.480515] block nvme0n1: no available path - failing I/O
[10524.480517] Buffer I/O error on dev nvme0n1, logical block 781402914, 
async page read
[10524.480524] block nvme0n1: no available path - failing I/O
[10524.480525] Buffer I/O error on dev nvme0n1, logical block 781402915, 
async page read
[10524.480528] block nvme0n1: no available path - failing I/O
[10524.480529] Buffer I/O error on dev nvme0n1, logical block 781402916, 
async page read
[10524.480531] block nvme0n1: no available path - failing I/O
[10524.480535] Buffer I/O error on dev nvme0n1, logical block 781402917, 
async page read
[10524.480539] block nvme0n1: no available path - failing I/O
[10524.480541] Buffer I/O error on dev nvme0n1, logical block 781402918, 
async page read
[10524.480546] block nvme0n1: no available path - failing I/O
[10524.480548] Buffer I/O error on dev nvme0n1, logical block 781402919, 
async page read

Thanks for your help
Wendy



             reply	other threads:[~2023-11-07  4:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  4:10 Wen Xiong [this message]
2023-11-07  4:36 ` Saw I/O errors while delete/create/attach a namespace on nvme device Chaitanya Kulkarni
2023-11-07  8:56 ` Christoph Hellwig
2023-11-07 10:25   ` Chaitanya Kulkarni
2023-11-07 14:31     ` Wen Xiong
2023-11-07 15:18       ` Keith Busch
2023-11-07 15:53         ` Wen Xiong
2023-11-07 19:22         ` Wen Xiong
2023-11-08  7:15         ` Christoph Hellwig
2023-11-07 13:26   ` Wen Xiong

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=ee222a8c6574d754d7e6355591e1a06a@linux.ibm.com \
    --to=wenxiong@linux.ibm.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=wenxiong@us.ibm.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 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.