From: Marc MERLIN <marc@merlins.org>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: dsterba@suse.cz, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: do not zero f_bavail if we have available space
Date: Wed, 19 Feb 2020 05:43:27 -0800 [thread overview]
Message-ID: <20200219134327.GD30993@merlins.org> (raw)
In-Reply-To: <2776783.E9KYCc1pZO@merkaba>
On Wed, Feb 19, 2020 at 10:17:24AM +0100, Martin Steigerwald wrote:
> Marc MERLIN - 19.02.20, 01:42:57 CET:
> > Has the patch gotten to any 5.5 release too?
>
> Yes, as git log easily reveals.
Sorry if I suck, but right now I only have pre-made kernel releases from
kernel.org.
This bug in 5.4 messed up some of my dm-thin volumes which now took 28% of a dm-thin
14TB pool when the actual data is only using 4GB :( (at the same time it
also shows my FS is full when of course it's not).
I'll likely have to destroy the dm-thin to recover that space (or maybe
not, we'll see), but I'm travelling and don't really have countless time
to allocate to this.
If 5.5.4 is supposed to fix this too, I'll build it, install it and hope
it reclaims my lost dm-thin space, and if not suck up the deletion,
re-creation and backup/restore.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2020-02-19 14:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:31 [PATCH] btrfs: do not zero f_bavail if we have available space Josef Bacik
2020-01-31 20:06 ` Martin Steigerwald
2020-02-01 1:00 ` Qu Wenruo
2020-02-02 17:52 ` David Sterba
[not found] ` <CAKhhfD7S=kcKLRURdNFZ8H4beS8=XjFvnOQXche7+SVOGFGC_w@mail.gmail.com>
2020-02-19 9:17 ` Martin Steigerwald
2020-02-19 13:43 ` Marc MERLIN [this message]
2020-02-19 14:31 ` David Sterba
2020-02-19 15:36 ` Marc MERLIN
2020-02-19 17:50 ` Roman Mamedov
2020-02-19 22:21 ` Martin Steigerwald
2020-02-20 21:46 ` Marc MERLIN
2020-02-21 5:38 ` Marc MERLIN
2020-02-21 5:45 ` Roman Mamedov
2020-02-21 23:07 ` btrfs filled up dm-thin and df%: shows 8.4TB of data used when I'm only using 10% of that Marc MERLIN
2020-02-21 23:17 ` How to roll back btrfs filesystem a few revisions? Marc MERLIN
2020-02-21 23:47 ` Josef Bacik
2020-02-22 0:08 ` Marc MERLIN
2020-02-22 0:36 ` Josef Bacik
2020-02-21 23:43 ` btrfs filled up dm-thin and df%: shows 8.4TB of data used when I'm only using 10% of that Josef Bacik
2020-02-22 0:01 ` Marc MERLIN
2020-02-22 0:43 ` Josef Bacik
2020-02-22 1:06 ` Marc MERLIN
2020-02-22 1:23 ` Marc MERLIN
2020-02-22 14:51 ` Marc MERLIN
2020-02-22 14:52 ` Josef Bacik
2020-02-22 15:24 ` Marc MERLIN
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=20200219134327.GD30993@merlins.org \
--to=marc@merlins.org \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
/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