[PATCH 0/4] Fixes for mkfs.xfs with high amount of CPUs and SSDs
Lukas Herbolt <[email protected]>
| Newsgroups | org.kernel.vger.fstests |
|---|---|
| Message-ID | <[email protected]> |
Since xfsprogs v6.13.0 mkfs.xfs scales the log size on SSDs with the amount
of CPUs. This leads to various failures from ENOSPC in generic/102 and generic172
(the xfs log can take up to 256MB on 1GB test FS) or depleting the dmthin
metadata area in generic/347. Downsize of the percentage change is we cannot
longer check the exact amount of data xfs_io wrote in the generic/102 test.
The xfs/21{6,7} are testing the old behavior before the concurrency option was
introduced. Forcing the old behavior on newer mkfs.xfs.
Lukas Herbolt (4):
common/rc: Add helper to calculate percetage of free space available
common/xfs: helper function to check if -l/-d/-r concurrecy flags.
generic/{102,172,347}: Adapt test for XFS on systems with 128+CPUs +
SSDs
xfs/216 xfs/217 Use default -l conccurency=0 on mkfs.xfs that supports
it
common/rc | 8 ++++++++
common/xfs | 6 ++++++
tests/generic/102 | 5 +++--
tests/generic/102.out | 20 ++++++++++----------
tests/generic/172 | 8 ++++----
tests/generic/347 | 9 ++++++++-
tests/xfs/216 | 9 +++++++--
tests/xfs/217 | 17 +++++++++++++++--
8 files changed, 61 insertions(+), 21 deletions(-)
--
2.53.0