From: Logan Gunthorpe <logang@xxxxxxxxxxxx> In some recent kernel versions, 00readonly fails with: mdadm: failed to set readonly for /dev/md0: Device or resource busy ERROR: array is not read-only! This was traced down to a race condition with udev holding a reference to the block device at the same time as trying to set it read only. To fix this, call udevadm settle before setting the array read only. Signed-off-by: Logan Gunthorpe <logang@xxxxxxxxxxxx> Acked-by: Coly Li <colyli@xxxxxxx> --- tests/00readonly | 1 + 1 file changed, 1 insertion(+) diff --git a/tests/00readonly b/tests/00readonly index 39202487..afe243b3 100644 --- a/tests/00readonly +++ b/tests/00readonly @@ -12,6 +12,7 @@ do $dev1 $dev2 $dev3 $dev4 --assume-clean check nosync check $level + udevadm settle mdadm -ro $md0 check readonly state=$(cat /sys/block/md0/md/array_state) -- 2.35.3
