From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v2 0/2] Some block rsv fixes
Date: Mon, 26 Oct 2020 16:57:25 -0400 [thread overview]
Message-ID: <cover.1603745723.git.josef@toxicpanda.com> (raw)
v1->v2:
- change the logic to max(1, root level), as generally we do not walk down into
level 0 for the merge, with the exception for root level == 0.
--- Original email ---
Hello,
Nikolay has noticed that -o enospc_debug was getting some warnings in
btrfs_use_block_rsv() on some tests. I dug into them and one class is easy to
fix as it's a straight regression. The other one is going to require some more
debugging, so in the meantime here's the two patches I have so far that can be
merged. The first is just to make my life easier when debugging these problems,
and the second is the actual regression fix. It should probably be tagged for
stable as well since the regression was backported to stable. Thanks,
Josef
Josef Bacik (2):
btrfs: print the block rsv type when we fail our reservation
btrfs: fix min reserved size calculation in merge_reloc_root
fs/btrfs/block-rsv.c | 3 ++-
fs/btrfs/relocation.c | 4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-26 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 20:57 Josef Bacik [this message]
2020-10-26 20:57 ` [PATCH v2 1/2] btrfs: print the block rsv type when we fail our reservation Josef Bacik
2020-10-27 8:55 ` Nikolay Borisov
2020-10-26 20:57 ` [PATCH v2 2/2] btrfs: fix min reserved size calculation in merge_reloc_root Josef Bacik
2020-10-27 8:53 ` Nikolay Borisov
2020-10-29 16:30 ` [PATCH v2 0/2] Some block rsv fixes David Sterba
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=cover.1603745723.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox