Btrfs: fix ENOSPC regressions
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | Btrfs: fix reservation code for mixed block groupsfs/ | +6 | 0 replies | |
| 2/4 | Btrfs: re-work delalloc flushingfs/ fs/ fs/ | +22 | 1 reply | |
| 3/4 | Btrfs: don't allocate chunks as aggressivelyfs/ | +8 | 2 replies | |
| 4/4 | Btrfs: rework how we reserve metadata bytesfs/ fs/ fs/ +1 more | +160 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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