From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/5] Fix global reserve size and can overcommit
Date: Fri, 16 Aug 2019 11:20:14 -0400 [thread overview]
Message-ID: <20190816152019.1962-1-josef@toxicpanda.com> (raw)
We hit a pretty crappy corner case in production that resulted in boxes slowing
down to a crawl.
can_overcommit() will not allow us to overcommit if there is not enough "real"
space to satisfy the global reserve. This is for hysterical raisins, we used to
not be able to allocate block groups a transaction commit time, so running out
of real space for the global reserve would result in an aborted transaction.
However that limitation was fixed years ago, so we no longer need to impose that
limitation on ourselves and can just overcommit with reckless abandon.
But this change exposed a bunch of corner cases in how we deal with very small
file systems. A lot of enospc related xfstests make very tiny file systems.
Btrfs by default gives you an 8mib metadata chunk. We default to having a
minimum global reserve size of 16mib. This is problematic.
Before we would allocate a new metadata chunk, which actually meant we were
"passing" these tests with 24mib metadata chunks but 256kib of used metadata,
and drastically less data space than was intended. With my change we started
failing these tests because we were no longer allocating the extra metadata
chunks.
The changes to the global reserve are to make it so we pass these xfstests, as
well as add some real hard logic to the minimum size of the global reserve,
rather than just an arbitrary 16mib. In practice those changes won't affect
real users because real users use more than 8mib of metadata and will get full
chunks.
These patches fix the original problem I intended to fix, and also have the nice
side-effect of making a bunch of the enospc xfstests finish _much_ faster. The
diffstat is as follows
fs/btrfs/block-rsv.c | 43 ++++++++++++++++++++++++++++++-------------
fs/btrfs/space-info.c | 51 +++++++++++++++++++++++++--------------------------
2 files changed, 55 insertions(+), 39 deletions(-)
Thanks,
Josef
next reply other threads:[~2019-08-16 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 15:20 Josef Bacik [this message]
2019-08-16 15:20 ` [PATCH 1/5] btrfs: change the minimum global reserve size Josef Bacik
2019-08-20 13:45 ` Nikolay Borisov
2019-08-20 19:12 ` Josef Bacik
2019-08-16 15:20 ` [PATCH 2/5] btrfs: always reserve our entire size for the global reserve Josef Bacik
2019-08-20 14:23 ` Nikolay Borisov
2019-08-20 19:13 ` Josef Bacik
2019-08-16 15:20 ` [PATCH 3/5] btrfs: use add_old_bytes when updating " Josef Bacik
2019-08-20 15:33 ` Nikolay Borisov
2019-08-16 15:20 ` [PATCH 4/5] btrfs: do not account global reserve in can_overcommit Josef Bacik
2019-08-21 6:51 ` Nikolay Borisov
2019-08-21 15:30 ` Vladimir Panteleev
2019-08-16 15:20 ` [PATCH 5/5] btrfs: add enospc debug messages for ticket failure Josef Bacik
2019-08-21 6:39 ` Nikolay Borisov
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=20190816152019.1962-1-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;
as well as URLs for NNTP newsgroup(s).