Skip to content

Btrfs: fix ENOSPC regressions

Josef Bacik linux-btrfs 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 3 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4Btrfs: fix reservation code for mixed block groupsfs/btrfs/extent-tree.c+6 -20 replies
2/4Btrfs: re-work delalloc flushingfs/btrfs/ctree.h fs/btrfs/extent-tree.c fs/btrfs/inode.c+22 -151 reply
3/4Btrfs: don't allocate chunks as aggressivelyfs/btrfs/extent-tree.c+8 -32 replies
4/4Btrfs: rework how we reserve metadata bytesfs/btrfs/ctree.h fs/btrfs/extent-tree.c fs/btrfs/relocation.c +1 more+160 -951 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] Btrfs: fix ENOSPC regressions

This patchset fixes some problems with the ENOSPC code for block groups, but more importantly it fixes a huge ENOSPC regression that's occured. With my fs_mark test

fs_mark -d /mnt/btrfs-test -D 512 -t 16 -n 4096 -F -S0

on a 2gb fs without these patches fs_mark would exit out with ENOSPC after writing around 50mb. With these patches I can now fill up the disk. Also the new ENOSPC code is super aggressive about allocating metadata chunks, to the point that even with the multi-writer regression fixed I was still only able to fill about 900mb with data on a 2gb fs. With all of these patches I can fill up the 2gb fs with about 1.9gb of data. This is much more reasonable. There doesn't appear to be any performance regression, but I would appreciate testing to make sure this is actually the case. Thanks,

Josef