From: Nilay Shroff <nilay@linux.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
axboe@fb.com, Gregory Joyce <gjoyce@ibm.com>
Subject: Re: [Bug Report] nvme-cli commands fails to open head disk node and print error
Date: Thu, 28 Mar 2024 15:55:45 +0530 [thread overview]
Message-ID: <4f10606c-654b-4ee8-9a91-a56bf49e0ecd@linux.ibm.com> (raw)
In-Reply-To: <20240328071552.GA18319@lst.de>
On 3/28/24 12:45, Christoph Hellwig wrote:
> On Thu, Mar 28, 2024 at 12:00:07PM +0530, Nilay Shroff wrote:
>> One of namespaces has zero disk capacity:
>>
>> # nvme id-ns /dev/nvme0 -n 0x3
>> NVME Identify Namespace 3:
>> nsze : 0
>> ncap : 0
>> nuse : 0
>> nsfeat : 0x14
>> nlbaf : 4
>> flbas : 0
>> <snip>
>
> How can you have a namespace with a zero capacity? NCAP is used
> as the check for legacy pre-ns scan controllers to check that
> the namespace exists.
>
>
I have this NVMe disk which has a namepsace with zero capacity.
# nvme list -v
Subsystem Subsystem-NQN Controllers
---------------- ------------------------------------------------------------------------------------------------ ----------------
nvme-subsys2 nqn.2019-10.com.kioxia:KCM7DRUG1T92:3D60A04906N1 nvme0, nvme2
<snip>
Device Generic NSID Usage Format Controllers
------------ ------------ ---------- -------------------------- ---------------- ----------------
/dev/nvme2n1 /dev/ng2n1 0x1 0.00 B / 46.01 GB 4 KiB + 0 B nvme0
nvme2n2 /dev/ng2n2 0x3 0.00 B / 0.00 B 512 B + 0 B nvme0
I didn't create that namespace with zero capacity and I didn't know about it until
recently I upgraded to 6.9-rc1 kernel. It became only apparent with latest kernel.
However as Daniel mentioned in another thread latest nvme-cli wouldn't exhibit the
issue I reported. And I'm going to wipe this namespace anyways.
Thanks,
--Nilay
next prev parent reply other threads:[~2024-03-28 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 6:30 [Bug Report] nvme-cli commands fails to open head disk node and print error Nilay Shroff
2024-03-28 7:15 ` Christoph Hellwig
2024-03-28 10:25 ` Nilay Shroff [this message]
2024-03-28 8:45 ` Daniel Wagner
2024-03-28 10:05 ` Nilay Shroff
2024-04-02 22:07 ` Kamaljit Singh
2024-04-03 3:07 ` Keith Busch
2024-04-03 10:10 ` Daniel Wagner
2024-04-02 15:04 ` Christoph Hellwig
2024-04-03 7:03 ` Nilay Shroff
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=4f10606c-654b-4ee8-9a91-a56bf49e0ecd@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@fb.com \
--cc=gjoyce@ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.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.