From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: dsterba@suse.cz, Martin Steigerwald <martin@lichtvoll.de>,
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 22:50:51 +0500 [thread overview]
Message-ID: <20200219225051.39ca1082@natsu> (raw)
In-Reply-To: <20200219153652.GA26873@merlins.org>
On Wed, 19 Feb 2020 07:36:52 -0800
Marc MERLIN <marc@merlins.org> wrote:
> Thanks. For some reason, debian's latest make-kpkg hangs forever on 5.5
> kernels (not sure why) so I can't build it right now, but I just got
> 5.4.20 and I'm compiling that now, thanks.
Debian deprecates their own tooling for regular users (as opposed to package
mantainers) to easily make custom kernel deb packages[1], they now suggest to
use the kernel-provided "make bindeb-pkg" instead.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925411#17
> As for dm-thin, I'm not sure yet, I'll find out when the new kernel is
> installed. I was also hoping fstrim would work, I guess I'll find out.
Indeed fstrim does deprovision backing storage on thin LVM just fine.
However I am not sure what is the relation with the bug being discussed. The
"zero f_bavail" was just returning "0" to df, while that was not actually
true. Seems puzzling how would that lead to increased usage of dm-thin for you.
--
With respect,
Roman
next prev parent reply other threads:[~2020-02-19 17:50 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
2020-02-19 14:31 ` David Sterba
2020-02-19 15:36 ` Marc MERLIN
2020-02-19 17:50 ` Roman Mamedov [this message]
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=20200219225051.39ca1082@natsu \
--to=rm@romanrm.net \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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 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.