All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Xiong <wenxiong@linux.ibm.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-nvme@lists.infradead.org, Wenxiong <wenxiong@us.ibm.com>
Subject: Re: Saw I/O errors while delete/create/attach a namespace on nvme device.
Date: Tue, 07 Nov 2023 08:31:37 -0600	[thread overview]
Message-ID: <dd07dbc043e38a7a4dcaee0b6d2835ec@linux.ibm.com> (raw)
In-Reply-To: <299987e5-ffb8-461c-9228-cad7e17cc542@nvidia.com>


> To check exactly which id is problematic something like in [1] can be
> used, totally untested ...
> 
Steps:
# nvme detach-ns /dev/nvme0 --namespace-id=1 --controllers=0x81
# nvme delete-ns /dev/nvme0 --namespace-id=1
# nvme create-ns /dev/nvme0 --nsze=562805846 --ncap=562805846 --flbas=0 
-dps=0 -nmic=1
# nvme attach-ns /dev/nvme0 -n 1  --controller=0x81

Below is linux log with your patch:

[  149.570987] nvme nvme0: rescanning namespaces.
[  149.578714] nguid mismatch
[  149.578719] nvme nvme0: identifiers changed for nsid 1
[  149.582291] block nvme0n1: no usable path - requeuing I/O
[  149.722140] block nvme0n1: no available path - failing I/O
[  149.722157] block nvme0n1: no available path - failing I/O
[  149.722165] Buffer I/O error on dev nvme0n1, logical block 281402912, 
async page read
[  149.722171] block nvme0n1: no available path - failing I/O
[  149.722175] Buffer I/O error on dev nvme0n1, logical block 281402913, 
async page read
[  149.722181] block nvme0n1: no available path - failing I/O
[  149.722185] Buffer I/O error on dev nvme0n1, logical block 281402914, 
async page read
[  149.722191] block nvme0n1: no available path - failing I/O
[  149.722195] Buffer I/O error on dev nvme0n1, logical block 281402915, 
async page read
[  149.722203] block nvme0n1: no available path - failing I/O
[  149.722208] Buffer I/O error on dev nvme0n1, logical block 281402916, 
async page read
[  149.722217] block nvme0n1: no available path - failing I/O
[  149.722226] Buffer I/O error on dev nvme0n1, logical block 281402917, 
async page read
[  149.722231] block nvme0n1: no available path - failing I/O
[  149.722233] Buffer I/O error on dev nvme0n1, logical block 281402918, 
async page read
[  149.722237] block nvme0n1: no available path - failing I/O
[  149.722239] Buffer I/O error on dev nvme0n1, logical block 281402919, 
async page read
[root@ltcrain119-lp4 ~]#

Below is nguid changes:
# nvme id-ns /dev/nvme0n1|grep nguid
nguid   : 37444630577000630025384700000245

  nvme id-ns /dev/nvme0n1|grep nguid
nguid   : 37444630577000630025384700000246

Thanks a lot!
Wendy


  reply	other threads:[~2023-11-07 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  4:10 Saw I/O errors while delete/create/attach a namespace on nvme device Wen Xiong
2023-11-07  4:36 ` Chaitanya Kulkarni
2023-11-07  8:56 ` Christoph Hellwig
2023-11-07 10:25   ` Chaitanya Kulkarni
2023-11-07 14:31     ` Wen Xiong [this message]
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=dd07dbc043e38a7a4dcaee0b6d2835ec@linux.ibm.com \
    --to=wenxiong@linux.ibm.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@infradead.org \
    --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.