Disk Says It is Full But There's Nothing on It

Keith Busch kbusch at kernel.org
Tue Aug 6 19:19:31 PDT 2024


On Tue, Aug 06, 2024 at 08:28:05PM +0000, Eric Robinson wrote:
> > someting bogus (nsze, ncap, nuse).
> 
> [root at 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.



More information about the Linux-nvme mailing list