Ronald Klop wrote:
> Wow,
>
> diskinfo.c has explicit support for regular files:
>
> But I would not know the proper use case for that related to the name of the
> tool.
I guess reading an imagefile, without needed to make an md device of it
first, I guess But hardly a "must have", in my o
;
But I would not know the proper use case for that related to the name of the
tool.
Anyways, nice catch. Computers are weird.
Cheers,
Ronald.
Van: Pete French
Datum: vrijdag, 25 februari 2022 11:30
Aan: Chuck Tuffli
CC: stable@freebsd.org
Onderwerp: Re: Instance drives in AWS comming up with
Ok, I found what was causing this, there is no bug, and I am somewhat
embarassed.
Somehow I ended up with a file called 'nda2' in /root
So doing 'diskinfo' in /root finds the file not the device. Simple as that.
sorry for the noise!
-pete.
On 24/02/2022 21:18, Chuck Tuffli wrote:
On Tue, Feb 22, 2022 at 1:16 PM Pete French wrote:
...
root@serpentine-vgay:/usr/home/webadmin # nvmecontrol identify nda2
Size:292968750 blocks
Capacity:292968750 blocks
Utilization: 2929687
On Tue, Feb 22, 2022 at 1:16 PM Pete French wrote:
...
> root@serpentine-vgay:/usr/home/webadmin # nvmecontrol identify nda2
> Size:292968750 blocks
> Capacity:292968750 blocks
> Utilization: 292968750 blocks
...
> LBA Format #00: Data Si
On 22/02/2022 19:51, Warner Losh wrote:
What does 'nvmecontrol identify nvme2' and 'nvmecontrol identify nda2'
say for each?
Warner
Umm, before I answer that, I have to say I found a new symptom. It only
shows me the wrong values if I am logged in on the serial console. If I
ssh in then
On Tue, Feb 22, 2022, 12:12 PM Pete French wrote:
> So, I have a number of machines in AWS. They are all of type r5a.xlarge
> which is supposed to have 140 gig of instance syorage on it. All these
> machines started life as clones of the same dirve, ro are runnign the
> same OS kernel, and they a
