public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Remi Gauvin <remi@georgianit.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: With Linux 5.5: Filesystem full while still 90 GiB free
Date: Fri, 31 Jan 2020 00:12:34 +0100	[thread overview]
Message-ID: <1746386.HyI1YD2b7T@merkaba> (raw)
In-Reply-To: <4b18e328-72fc-8167-d140-97c898c47e6a@georgianit.com>

Remi Gauvin - 30.01.20, 22:20:47 CET:
> On 2020-01-30 4:10 p.m., Martin Steigerwald wrote:
> > I am done with re-balancing experiments.
> 
> It should be pretty easy to fix.. use the metadata_ratio=1 mount
> option, then write enough to force the allocation of more data
> space,,
> 
> In your earlier attempt, you wrote 500MB, but from your btrfs
> filesystem usage, you had over 1GB of allocated but unused space.
> 
> If you wrote and deleted, say, 20GB of zeroes, that should force the
> allocation of metatada space to get you past the global reserve size
> that is causing this bug,, (Assuming this bug is even impacting you. 
> I was unclear from your messages if you are seeing any ill effects
> besides the misreporting in df.)

I thought more about writing a lot of little files as I expect that to 
use more metadata, but… I can just work around it by using command line 
tools instead of Dolphin to move data around. This is mostly my music, 
photos and so on filesystem, I do not change data on it very often, so 
that will most likely work just fine for me until there is a proper fix.

So do need to do any more things that could potentially age the 
filesystem. :)

-- 
Martin



  reply	other threads:[~2020-01-30 23:12 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
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 [this message]
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=1746386.HyI1YD2b7T@merkaba \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=remi@georgianit.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox