Date: Thu, 24 Feb 2022 13:18:29 -0800 From: Chuck Tuffli <ctuffli@gmail.com> To: Pete French <pete@twisted.org.uk> Cc: stable@freebsd.org Subject: Re: Instance drives in AWS comming up with the wrong size Message-ID: <CAKAYmML2=j84Vq__Zn4qJaqFkgNVGAaCPk9qa=hvYX13kFSnjw@mail.gmail.com> In-Reply-To: <82956746-91aa-4744-c12f-40c5ff7c3f39@twisted.org.uk> References: <b6fae531-edaf-d7c1-f6be-32c966fd711c@twisted.org.uk> <CANCZdfrye3mBj5Ej=vjoUUtKx%2BqNX%2BXBXq15j6B0FCnZDZw54Q@mail.gmail.com> <82956746-91aa-4744-c12f-40c5ff7c3f39@twisted.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 22, 2022 at 1:16 PM Pete French <pete@twisted.org.uk> wrote:
...
> root@serpentine-vgay:/usr/home/webadmin # nvmecontrol identify nda2
> Size: 292968750 blocks
> Capacity: 292968750 blocks
> Utilization: 292968750 blocks
...
> LBA Format #00: Data Size: 512 Metadata Size: 0 Performance: Best
This says the capacity is 140GB which matches with your expectations
if I'm understanding correctly. Can you run:
nvmecontrol identify nvme2 | grep "Serial Number"
via both ssh and from the serial console?
--chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKAYmML2=j84Vq__Zn4qJaqFkgNVGAaCPk9qa=hvYX13kFSnjw>