Re: With Linux 5.5: Filesystem full while still 90 GiB free

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martin Raiber - 29.01.20, 21:04:41 CET:
> On 29.01.2020 20:33 Martin Steigerwald wrote:
> > I thought this would not happen anymore, but see yourself:
> > 
> > % LANG=en df -hT /daten
> > Filesystem             Type   Size  Used Avail Use% Mounted on
> > /dev/mapper/sata-daten btrfs  400G  310G     0 100% /daten
> > 
> > I removed some larger files but to no avail.
> 
> I have the same issue since 5.4. This patch should fix it:
> https://lore.kernel.org/linux-btrfs/f1f1a2ab-ed09-d841-6a93-a44a8fb231
> 2f@xxxxxxx/T/ Confirm by writing to the file system. It shouldn't say
> that it is out of space (only df report says zero).
> 
> As far as I know, it is unfortunately not fixed in any released kernel
> yet.

Indeed remaining metadata space in the one 1 GiB big metadata chunk is 
less than global reserve:

> > However, also according to btrfs fi usage it is perfectly good:
> > 
> > % btrfs fi usage -T /daten
> > 
> > Overall:
> >     Device size:                 400.00GiB
> >     Device allocated:            311.04GiB
> >     Device unallocated:           88.96GiB
> >     Device missing:                  0.00B
> >     Used:                        309.50GiB
> >     Free (estimated):             90.16GiB      (min: 90.16GiB)
> >     Data ratio:                       1.00
> >     Metadata ratio:                   1.00
> >     Global reserve:              364.03MiB      (used: 0.00B)
> >     
> >                           Data      Metadata  System
> > 
> > Id Path                   single    single    single   Unallocated
> > -- ---------------------- --------- --------- -------- -----------
> > 
> >  1 /dev/mapper/sata-daten 310.00GiB   1.01GiB 32.00MiB    88.96GiB
> > 
> > -- ---------------------- --------- --------- -------- -----------
> > 
> >    Total                  310.00GiB   1.01GiB 32.00MiB    88.96GiB
> >    Used                   308.80GiB 714.67MiB 64.00KiB

Hmmm, Dolphin file manager said out of space, but it may be cause it 
meanwhile checks for enough available space *before* initiating the copy 
or move operation.

Consequently using "mv" worked to move the files to that filesystem.

Thank you for that hint.

So if its just a cosmetic issue then I can wait for the patch to land in 
linux-stable. Or does it still need testing?

Best,
-- 
Martin





[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux