From: Keith Busch <kbusch@kernel.org>
To: Eric Robinson <eric.robinson@psmnv.com>
Cc: Daniel Wagner <dwagner@suse.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Disk Says It is Full But There's Nothing on It
Date: Tue, 6 Aug 2024 19:19:31 -0700 [thread overview]
Message-ID: <ZrLZs2ZpxcM1XcV_@kbusch-mbp> (raw)
In-Reply-To: <SJ0PR03MB650188563CEBA3B2E6D2130BFABF2@SJ0PR03MB6501.namprd03.prod.outlook.com>
On Tue, Aug 06, 2024 at 08:28:05PM +0000, Eric Robinson wrote:
> > someting bogus (nsze, ncap, nuse).
>
> [root@store11b zpool0]# nvme id-ns /dev/nvme0n1
> NVME Identify Namespace 1:
> nsze : 0x6fc400000
> ncap : 0x6fc400000
> nuse : 0x6fc400000
> nsfeat : 0
Is this after a fresh format? If you've no data on here that you wish to
save, run something like
# blkdiscard /dev/nvme0n1
or
# nvme format /dev/nvme0n1 -f
and see if it changes. If it still doesn't change, then you need to
check with your vendor on the discrepency because nvme-cli is just the
messenger and faithfully shows what the device reports.
In my experience, about half of nvme devices always report nuse == nsze.
LBA allocation tracking is an optional feature that many devices don't
do, but since you apparently have the exact same model and firmware that
shows it implementing this option, that's just weird.
next prev parent reply other threads:[~2024-08-07 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 23:30 Disk Says It is Full But There's Nothing on It Eric Robinson
2024-08-06 11:42 ` Daniel Wagner
2024-08-06 13:11 ` Eric Robinson
2024-08-06 20:05 ` Daniel Wagner
2024-08-06 20:28 ` Eric Robinson
2024-08-07 2:19 ` Keith Busch [this message]
2024-08-07 3:27 ` Eric Robinson
2024-08-08 19:28 ` Eric Robinson
2024-08-08 22:16 ` Keith Busch
2024-08-08 22:37 ` Eric Robinson
2024-08-07 2:22 ` Keith Busch
2024-08-07 3:30 ` Eric Robinson
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=ZrLZs2ZpxcM1XcV_@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=dwagner@suse.de \
--cc=eric.robinson@psmnv.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox