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

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

[Eric Robinson]

Two new Dell R640 servers, same OS and firmware.  One of the servers shows the drive usage correctly, as they don't have anything on them yet...

[root@store11a ~]# nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            7170A00CTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.50  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme1n1          /dev/ng1n1            6240A0XMTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.49  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme2n1          /dev/ng2n1            6240A0T8TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.48  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme3n1          /dev/ng3n1            6240A1LRTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.48  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme4n1          /dev/ng4n1            6240A0XWTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.47  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme5n1          /dev/ng5n1            6240A0XZTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.47  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme6n1          /dev/ng6n1            6240A1H0TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.47  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme7n1          /dev/ng7n1            6240A0T4TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.47  MB /  15.36  TB    512   B +  0 B   2.2.1

The other servers shows that the drives are completely full.

[root@store11c ~]# nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            6240A0Y0TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme1n1          /dev/ng1n1            6240A0T2TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme2n1          /dev/ng2n1            6230A0N9TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme3n1          /dev/ng3n1            62D0A0FFTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme4n1          /dev/ng4n1            62D0A0FPTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme5n1          /dev/ng5n1            6240A0XNTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme6n1          /dev/ng6n1            6240A1BJTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme7n1          /dev/ng7n1            6240A0Q4TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         15.36  TB /  15.36  TB    512   B +  0 B   2.2.1

I have not been able to find any hidden partitions or data on the drives.

What's up with this?


-Eric




Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Daniel Wagner]

On Mon, Aug 05, 2024 at 11:30:02PM GMT, Eric Robinson wrote:
> What's up with this?

There was a bug in nvme-cli which got the usage sizes reporting wrong.
Could you check with the lastest upstream version?

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

[Eric Robinson]

> -----Original Message-----
> From: Daniel Wagner <dwagner@suse.de>
> Sent: Tuesday, August 6, 2024 6:42 AM
> To: Eric Robinson <eric.robinson@psmnv.com>
> Cc: linux-nvme@lists.infradead.org
> Subject: Re: Disk Says It is Full But There's Nothing on It
>
> On Mon, Aug 05, 2024 at 11:30:02PM GMT, Eric Robinson wrote:
> > What's up with this?
>
> There was a bug in nvme-cli which got the usage sizes reporting wrong.
> Could you check with the lastest upstream version?

I was on 2.6.5. I upgraded to 2.9.1 but got the same result.

-Eric


Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Daniel Wagner]

On Tue, Aug 06, 2024 at 01:11:23PM GMT, Eric Robinson wrote:

> I was on 2.6.5. I upgraded to 2.9.1 but got the same result.

I assume you also update libnvme alongside, because the bug was in
libnvme. Anyway, what do you get with:

nvme id-ns /dev/nvme0n1

This should help to figure out if nvme-cli gets it wrong or the device
reports someting bogus (nsze, ncap, nuse).

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

[Eric Robinson]

> -----Original Message-----
> From: Daniel Wagner <dwagner@suse.de>
> Sent: Tuesday, August 6, 2024 3:06 PM
> To: Eric Robinson <eric.robinson@psmnv.com>
> Cc: linux-nvme@lists.infradead.org
> Subject: Re: Disk Says It is Full But There's Nothing on It
>
> On Tue, Aug 06, 2024 at 01:11:23PM GMT, Eric Robinson wrote:
>
> > I was on 2.6.5. I upgraded to 2.9.1 but got the same result.
>
> I assume you also update libnvme alongside, because the bug was in libnvme.

Yes, I upgraded to libnvme 1.6.1.

> Anyway, what do you get with:
>
> nvme id-ns /dev/nvme0n1
>
> This should help to figure out if nvme-cli gets it wrong or the device reports
> 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
nlbaf   : 4
flbas   : 0
mc      : 0x3
dpc     : 0x1f
dps     : 0
nmic    : 0x1
rescap  : 0xff
fpi     : 0x80
dlfeat  : 1
nawun   : 0
nawupf  : 0
nacwu   : 0
nabsn   : 0
nabo    : 0
nabspf  : 0
noiob   : 0
nvmcap  : 15360950534144
mssrl   : 0
mcl     : 0
msrc    : 0
nulbaf  : 0
anagrpid: 0
nsattr  : 0
nvmsetid: 0
endgid  : 0
nguid   : 3647373054a015890025384100000002
eui64   : 0000000000000000
lbaf  0 : ms:0   lbads:9  rp:0x1 (in use)
lbaf  1 : ms:8   lbads:9  rp:0x3
lbaf  2 : ms:0   lbads:12 rp:0
lbaf  3 : ms:8   lbads:12 rp:0x2
lbaf  4 : ms:64  lbads:12 rp:0x3
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Keith Busch]

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.

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

[Eric Robinson]

> -----Original Message-----
> From: Keith Busch <kbusch@kernel.org>
> Sent: Tuesday, August 6, 2024 9:20 PM
> To: Eric Robinson <eric.robinson@psmnv.com>
> Cc: Daniel Wagner <dwagner@suse.de>; linux-nvme@lists.infradead.org
> Subject: Re: Disk Says It is Full But There's Nothing on It
>
> 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
>

That did the trick. First, I issued the blkdiscard command against /dev/nvme0n1. I then ran nvme list several times in a row, and each time I could see the Used column decreasing. Clearly the drive was doing cleanup. I then ran blkdiscard for all the other drives in sequence. Each time it took 24 seconds to return to a prompt. At the end, I ran nvme list again, with the following results. It is obvious that each of the drives is going through a discard process.

[root@store11c ~]# nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            6240A0Y0TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          1.18  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme1n1          /dev/ng1n1            6240A0T2TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          4.37  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme2n1          /dev/ng2n1            6230A0N9TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          5.92  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme3n1          /dev/ng3n1            62D0A0FFTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          7.74  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme4n1          /dev/ng4n1            62D0A0FPTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1          9.24  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme5n1          /dev/ng5n1            6240A0XNTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         11.04  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme6n1          /dev/ng6n1            6240A1BJTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.63  TB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme7n1          /dev/ng7n1            6240A0Q4TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         14.04  TB /  15.36  TB    512   B +  0 B   2.2.1

And then finally, after a few minutes...

[root@store11c ~]# nvme list
Node                  Generic               SN                   Model                                    Namespace  Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            6240A0Y0TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme1n1          /dev/ng1n1            6240A0T2TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme2n1          /dev/ng2n1            6230A0N9TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme3n1          /dev/ng3n1            62D0A0FFTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme4n1          /dev/ng4n1            62D0A0FPTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme5n1          /dev/ng5n1            6240A0XNTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme6n1          /dev/ng6n1            6240A1BJTCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
/dev/nvme7n1          /dev/ng7n1            6240A0Q4TCG8         Dell Ent NVMe CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1

...success.

> 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.
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Eric Robinson]

> -----Original Message-----
> From: Linux-nvme <linux-nvme-bounces@lists.infradead.org> On Behalf Of Eric
> Robinson
> Sent: Tuesday, August 6, 2024 10:28 PM
> To: Keith Busch <kbusch@kernel.org>
> Cc: Daniel Wagner <dwagner@suse.de>; linux-nvme@lists.infradead.org
> Subject: RE: Disk Says It is Full But There's Nothing on It
>
> > -----Original Message-----
> > From: Keith Busch <kbusch@kernel.org>
> > Sent: Tuesday, August 6, 2024 9:20 PM
> > To: Eric Robinson <eric.robinson@psmnv.com>
> > Cc: Daniel Wagner <dwagner@suse.de>; linux-nvme@lists.infradead.org
> > Subject: Re: Disk Says It is Full But There's Nothing on It
> >
> > 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
> >
>
> That did the trick. First, I issued the blkdiscard command against /dev/nvme0n1.
> I then ran nvme list several times in a row, and each time I could see the Used
> column decreasing. Clearly the drive was doing cleanup. I then ran blkdiscard
> for all the other drives in sequence. Each time it took 24 seconds to return to a
> prompt. At the end, I ran nvme list again, with the following results. It is obvious
> that each of the drives is going through a discard process.
>
> [root@store11c ~]# nvme list
> Node                  Generic               SN                   Model
> Namespace  Usage                      Format           FW Rev
> --------------------- --------------------- -------------------- ---------------------------------------
> - ---------- -------------------------- ---------------- --------
> /dev/nvme0n1          /dev/ng0n1            6240A0Y0TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1          1.18  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme1n1          /dev/ng1n1            6240A0T2TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1          4.37  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme2n1          /dev/ng2n1            6230A0N9TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1          5.92  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme3n1          /dev/ng3n1            62D0A0FFTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1          7.74  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme4n1          /dev/ng4n1            62D0A0FPTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1          9.24  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme5n1          /dev/ng5n1            6240A0XNTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         11.04  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme6n1          /dev/ng6n1            6240A1BJTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.63  TB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme7n1          /dev/ng7n1            6240A0Q4TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         14.04  TB /  15.36  TB    512   B +  0 B   2.2.1
>
> And then finally, after a few minutes...
>
> [root@store11c ~]# nvme list
> Node                  Generic               SN                   Model
> Namespace  Usage                      Format           FW Rev
> --------------------- --------------------- -------------------- ---------------------------------------
> - ---------- -------------------------- ---------------- --------
> /dev/nvme0n1          /dev/ng0n1            6240A0Y0TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme1n1          /dev/ng1n1            6240A0T2TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme2n1          /dev/ng2n1            6230A0N9TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme3n1          /dev/ng3n1            62D0A0FFTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme4n1          /dev/ng4n1            62D0A0FPTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme5n1          /dev/ng5n1            6240A0XNTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme6n1          /dev/ng6n1            6240A1BJTCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
> /dev/nvme7n1          /dev/ng7n1            6240A0Q4TCG8         Dell Ent NVMe
> CM6 RI 15.36TB             0x1         12.82  MB /  15.36  TB    512   B +  0 B   2.2.1
>
> ...success.
>
> > 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.

I thought we resolved it, but one of the three servers refuses to change. It continues to show the drive capacity fully used. I noticed that the drives have newer firmware than the other servers. The NVME drives in the one that won't cooperate have FW 2.3.0, whereas the ones that worked have FW 2.2.1, if that matters.

-Eric




Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Keith Busch]

On Thu, Aug 08, 2024 at 07:28:11PM +0000, Eric Robinson wrote:
> I thought we resolved it, but one of the three servers refuses to
> change. It continues to show the drive capacity fully used. I noticed
> that the drives have newer firmware than the other servers. The NVME
> drives in the one that won't cooperate have FW 2.3.0, whereas the ones
> that worked have FW 2.2.1, if that matters.

You should talk to your vendor.
 
> Disclaimer : This email and any files transmitted with it are
> confidential and intended solely for intended recipients. If you are
> not the named addressee you should not disseminate, distribute, copy
> or alter this email. Any views or opinions presented in this email are

...

You should know there are plenty of free email providers that don't
append disclaimers that are fundamentally incompatible with public
mailing lists. This is the last message I'll reply to if it has this
disclaimer because I do not want access to any "confidential" emails.

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

[Eric Robinson]

> -----Original Message-----
> From: Keith Busch <kbusch@kernel.org>
> Sent: Thursday, August 8, 2024 5:17 PM
> To: Eric Robinson <eric.robinson@psmnv.com>
> Cc: Daniel Wagner <dwagner@suse.de>; linux-nvme@lists.infradead.org
> Subject: Re: Disk Says It is Full But There's Nothing on It
>
> On Thu, Aug 08, 2024 at 07:28:11PM +0000, Eric Robinson wrote:
> > I thought we resolved it, but one of the three servers refuses to
> > change. It continues to show the drive capacity fully used. I noticed
> > that the drives have newer firmware than the other servers. The NVME
> > drives in the one that won't cooperate have FW 2.3.0, whereas the ones
> > that worked have FW 2.2.1, if that matters.
>
> You should talk to your vendor.
>

I reached out to them.

>
> You should know there are plenty of free email providers that don't append
> disclaimers that are fundamentally incompatible with public mailing lists.


We use Office 365. The disclaimer is a corporate level policy. I think most organizations don't use disclaimers anymore, as they're not legally binding and they're basically white noise that the human eye typically skips right over. Maybe our compliance folks will change it if they get enough complaints, but I think you're the second or third person to mention it since it was established in the late 90's or early 2000's.


> This is the last message I'll reply to if it has this disclaimer because I
> do not want access to any "confidential" emails.

Understood.

-Eric
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

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

[Keith Busch]

On Tue, Aug 06, 2024 at 08:28:05PM +0000, Eric Robinson wrote:
> Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
> 

Please fix your email client. This message is not appropriate for public
mailing lists.

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

[Eric Robinson]

> -----Original Message-----
> From: Keith Busch <kbusch@kernel.org>
> Sent: Tuesday, August 6, 2024 9:22 PM
> To: Eric Robinson <eric.robinson@psmnv.com>
> Cc: Daniel Wagner <dwagner@suse.de>; linux-nvme@lists.infradead.org
> Subject: Re: Disk Says It is Full But There's Nothing on It
>
> On Tue, Aug 06, 2024 at 08:28:05PM +0000, Eric Robinson wrote:
> > Disclaimer : This email and any files transmitted with it are confidential and
> intended solely for intended recipients. If you are not the named addressee you
> should not disseminate, distribute, copy or alter this email. Any views or
> opinions presented in this email are solely those of the author and might not
> represent those of Physician Select Management. Warning: Although Physician
> Select Management has taken reasonable precautions to ensure no viruses are
> present in this email, the company cannot accept responsibility for any loss or
> damage arising from the use of this email or attachments.
> >
>
> Please fix your email client. This message is not appropriate for public mailing
> lists.

That's not my email client. The disclaimer is appended by our corporate email provider and has been that way for a couple of decades. Not much I can do about it. Someone comments on it about once per decade. 😊




Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.