]> git.baikalelectronics.ru Git - kernel.git/commitdiff
btrfs: reduce the preemptive flushing threshold to 90%
authorJosef Bacik <josef@toxicpanda.com>
Wed, 11 Aug 2021 18:37:15 +0000 (14:37 -0400)
committerDavid Sterba <dsterba@suse.com>
Mon, 23 Aug 2021 11:19:15 +0000 (13:19 +0200)
The preemptive flushing code was added in order to avoid needing to
synchronously wait for ENOSPC flushing to recover space.  Once we're
almost full however we can essentially flush constantly.  We were using
98% as a threshold to determine if we were simply full, however in
practice this is a really high bar to hit.  For example reports of
systems running into this problem had around 94% usage and thus
continued to flush.  Fix this by lowering the threshold to 90%, which is
a more sane value, especially for smaller file systems.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212185
CC: stable@vger.kernel.org # 5.12+
Fixes: e17432c33757 ("btrfs: improve preemptive background space flushing")
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/space-info.c

index d9c8d738678f0d91a00c90424f1733e75627c2fc..cab532a48bcd56bc2a83535a607af964f26e3d38 100644 (file)
@@ -733,7 +733,7 @@ static bool need_preemptive_reclaim(struct btrfs_fs_info *fs_info,
 {
        u64 global_rsv_size = fs_info->global_block_rsv.reserved;
        u64 ordered, delalloc;
-       u64 thresh = div_factor_fine(space_info->total_bytes, 98);
+       u64 thresh = div_factor_fine(space_info->total_bytes, 90);
        u64 used;
 
        /* If we're just plain full then async reclaim just slows us down. */