The dirhash_collide generates filenames from arbitrary random bytes (only '.' and '/' are filtered out), which are not valid UTF-8 in general. Catalog names on both classic HFS and HFS+ are Unicode. Feeding random bytes causes fsck to report "Illegal name" or catalog corruption that has nothing to do with directory hash-collision handling, which is what this test is actually meant to exercise. This patch excludes HFS/HFS+ file systems from generic/339 run. Signed-off-by: Viacheslav Dubeyko --- tests/generic/339 | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/tests/generic/339 b/tests/generic/339 index bf8f7729..5cc1086f 100755 --- a/tests/generic/339 +++ b/tests/generic/339 @@ -17,6 +17,15 @@ _begin_fstest auto dir _require_scratch _require_test_program "dirhash_collide" +# dirhash_collide generates filenames from arbitrary random bytes (only +# '.' and '/' are filtered out), which are not valid UTF-8 in general. +# Catalog names on both classic HFS and HFS+ are Unicode. Feeding random +# bytes causes fsck to report "Illegal name" / catalog corruption that has +# nothing to do with directory hash-collision handling, which is what this +# test is actually meant to exercise. +_exclude_fs hfs +_exclude_fs hfsplus + _scratch_mkfs >>$seqres.full 2>&1 _scratch_mount -- 2.43.0