Hi all,
After generic/232 failure has been reported and resolved[1], I still
could see fstests generic/233 failure on ext4 with v4.14-rc3 kernel.
This is not 100% reproduced (block usage needs to exceed soft limit) but
reliably.
seed = S
Comparing user usage
-Comparing group usage
+4c4
+< #1001 +- 32064 32000 32000 998 1000 1000
+---
+> #1001 +- 32064 32000 32000 7days 998 1000 1000
Grace time was not printed by repquota right after the fsstress run when
we exceeded the block soft limit, and only printed after a quotacheck
was run. With v4.13 kernel, block grace time could be printed
immediately after the fsstress run.
git bisect pointed the first bad to commit 7b9ca4c61bc2 ("quota: Reduce
contention on dq_data_lock"). And I've confirmed the bisection result by
converting the commit in question and running generic/233 for 20
iterations without a failure.
Thanks,
Eryu
[1] https://www.spinics.net/lists/linux-ext4/msg58372.html
