[PATCH 33/33] fuse2fs: hack around weird corruption problems

Darrick J. Wong
2025-10-29T01:29:02Z

generic/113 seems to blow up fuse+iomap and the fs doesnt even get
marked corrupt so yeah

XXX DO NOT MERGE

Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
---
common/rc | 7 +++++++
tests/generic/223 | 4 ++++
2 files changed, 11 insertions(+)

diff --git a/common/rc b/common/rc
index b6e76c03a12445..ea991526105990 100644
--- a/common/rc
+++ b/common/rc
@@ -1658,6 +1658,13 @@ _repair_test_fs()
$tmp.repair 2>&1
res=$?
;;
+ ext[234])
+ e2fsck -f -y $TEST_DEV >$tmp.repair 2>&1
+ res=$?
+ if test "$res" -lt 4 ; then
+ res=0
+ fi
+ ;;
*)
local fsopts=
if [[ "$FSTYP" =~ ext[234]$ ]]; then
diff --git a/tests/generic/223 b/tests/generic/223
index ccb17592102a8d..dcf7ef64ac5dbe 100755
--- a/tests/generic/223
+++ b/tests/generic/223
@@ -16,6 +16,10 @@ _begin_fstest auto quick prealloc
_require_scratch
_require_xfs_io_command "falloc"

+if [[ "$FSTYP" =~ fuse.ext[234] ]]; then
+ _notrun "fuse2fs does not do stripe-aligned allocation"
+fi
+
BLOCKSIZE=4096

for SUNIT_K in 8 16 32 64 128; do