https://bugzilla.novell.com/show_bug.cgi?id=793954
https://bugzilla.novell.com/show_bug.cgi?id=793954#c50
--- Comment #50 from Neil Brown 2013-04-29 06:05:46 UTC ---
Hi Volker.
Your latest details seem to just confirm that udev is doing thing when I
believe that it shouldn't. The call to "udevadm settle" earlier in boot.md
should wait for all those udev events to happen. It very much seems like it
does.
Only they still come, which seems to suggest that something else is triggering
new 'add' events, though I cannot imaging what.
Could you try something new for me?
in boot.md, add the line
/sbin/udevadm control --stop-exec-queue
before
$mdadm_BIN -IRs
$mdadm_BIN -A -s -c $mdadm_CONFIG
# a status of 2 is not an error
test $? -eq 0 -o $? -eq 2
rc_status -v
and add
/sbin/udevadm control --start-exec-queue
just after that section.
This should ensure that udev and boot.md don't race. It might slow boot by 5
seconds but that might be better than races.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.