As explained in the commit 0e7aabe55e8a ("md/002: use --run option instead of "echo y""), "echo y" and pipe no longer work with the mdadm command since mdadm version 4.4. The commit fixed this problem. However, when the commit cefc4288c469 ("md/rc: add _md_atomics_test") introduced the helper function _md_atomics_test to factor out the test content in md/002, the fix was not propagated. Then, md/002 and md/003 do not work with mdadm version 4.4 again. Fix it again by using --run option instead of "echo y". Fixes: cefc4288c469 ("md/rc: add _md_atomics_test") Signed-off-by: Shin'ichiro Kawasaki --- tests/md/rc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/tests/md/rc b/tests/md/rc index 14f4170..d48282f 100644 --- a/tests/md/rc +++ b/tests/md/rc @@ -201,10 +201,10 @@ _md_atomics_test() { if [ "$personality" = raid0 ] || [ "$personality" = raid10 ] then - echo y | mdadm --create /dev/md/blktests_md --level=$personality \ - --chunk="${md_chunk_size_kb}"K \ - --raid-devices=4 --force /dev/"${dev0}" /dev/"${dev1}" \ - /dev/"${dev2}" /dev/"${dev3}" 2> /dev/null 1>&2 + mdadm --create /dev/md/blktests_md --level=$personality \ + --run --chunk="${md_chunk_size_kb}"K \ + --raid-devices=4 --force /dev/"${dev0}" /dev/"${dev1}" \ + /dev/"${dev2}" /dev/"${dev3}" 2> /dev/null 1>&2 atomics_boundaries_unit_max=$(_md_atomics_boundaries_max "$raw_atomic_write_boundary" $md_chunk_size "1") atomics_boundaries_max=$(_md_atomics_boundaries_max "$raw_atomic_write_boundary" "$md_chunk_size" "0") @@ -220,9 +220,9 @@ _md_atomics_test() { if [ "$personality" = raid1 ] then - echo y | mdadm --create /dev/md/blktests_md --level=$personality \ - --raid-devices=4 --force /dev/"${dev0}" /dev/"${dev1}" \ - /dev/"${dev2}" /dev/"${dev3}" 2> /dev/null 1>&2 + mdadm --create /dev/md/blktests_md --level=$personality \ + --run --raid-devices=4 --force /dev/"${dev0}" /dev/"${dev1}" \ + /dev/"${dev2}" /dev/"${dev3}" 2> /dev/null 1>&2 md_dev=$(readlink /dev/md/blktests_md | sed 's|\.\./||') fi -- 2.51.0