From: Martin Steigerwald <martin@lichtvoll.de>
To: Martin Raiber <martin@urbackup.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: With Linux 5.5: Filesystem full while still 90 GiB free
Date: Wed, 29 Jan 2020 22:20:02 +0100 [thread overview]
Message-ID: <2049829.BAvHWrS4Fr@merkaba> (raw)
In-Reply-To: <0102016ff2e7e3ad-6b776470-32f1-4b3d-9063-d3c96921df89-000000@eu-west-1.amazonses.com>
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@gmx.com/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
next prev parent reply other threads:[~2020-01-29 21:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 19:33 With Linux 5.5: Filesystem full while still 90 GiB free Martin Steigerwald
2020-01-29 20:04 ` Martin Raiber
2020-01-29 21:20 ` Martin Steigerwald [this message]
2020-01-29 22:55 ` Chris Murphy
2020-01-30 10:41 ` Martin Steigerwald
2020-01-30 16:37 ` Chris Murphy
2020-01-30 20:02 ` Martin Steigerwald
2020-01-30 20:18 ` Chris Murphy
2020-01-30 20:59 ` Josef Bacik
2020-01-30 21:09 ` Chris Murphy
2020-01-30 21:32 ` Martin Raiber
2020-01-30 21:42 ` Josef Bacik
2020-01-30 21:12 ` Martin Steigerwald
2020-01-30 21:10 ` Martin Steigerwald
2020-01-30 21:20 ` Remi Gauvin
2020-01-30 23:12 ` Martin Steigerwald
2020-01-31 1:43 ` Matt Corallo
2020-01-31 1:57 ` Qu Wenruo
2020-03-02 1:57 ` Etienne Champetier
2020-03-02 1:59 ` Qu Wenruo
2020-01-31 4:12 ` Etienne Champetier
2020-01-30 17:19 ` David Sterba
2020-01-30 19:31 ` Chris Murphy
2020-01-30 19:58 ` Martin Steigerwald
2020-01-31 3:00 ` Zygo Blaxell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2049829.BAvHWrS4Fr@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@urbackup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.