https://bugzilla.novell.com/show_bug.cgi?id=793954
https://bugzilla.novell.com/show_bug.cgi?id=793954#c46
--- Comment #46 from Volker Kuhlmann 2013-04-12 17:18:03 NZST ---
It occurred to me that stracing the mdadm run by boot.md would give only a
small part of the picture, and logging *ALL* invocations of mdadm including
location and arguments would be more interesting. So I put a wrapper script
around /sbin/mdadm.
The problem appears to be a race between udev and boot.md. The -IRs and -A
-s... are run by boot.md, the others by udev.
This gives a degraded array:
+ : mdadm --detail --export /dev/md0
+ : mdadm -IRs
+ : mdadm --examine --export /dev/sdb5
+ : mdadm --examine --export /dev/sda5
+ : mdadm --examine --export /dev/sda3
+ : mdadm --examine --export /dev/sdb3
+ : mdadm -A -s -c /etc/mdadm.conf
+ : mdadm --incremental /dev/sdb3
+ : mdadm --incremental /dev/sdb5
+ : mdadm --incremental /dev/sda5
+ : mdadm --incremental /dev/sda3
This works fine:
+ : mdadm --detail --export /dev/md0
+ : mdadm -IRs
+ : mdadm -A -s -c /etc/mdadm.conf
+ : mdadm --examine --export /dev/sdb3
+ : mdadm --examine --export /dev/sda3
+ : mdadm --examine --export /dev/sdb5
+ : mdadm --examine --export /dev/sda5
+ : mdadm --incremental /dev/sdb3
+ : mdadm --incremental /dev/sdb5
+ : mdadm --incremental /dev/sda3
+ : mdadm --incremental /dev/sda5
So udev stoidly examines all partitions and then runs incremental. Meanwhile
boot.md has already run incremental and at some point assembles the arrays.
What I don't understand is why both of them are doing the same job. How much do
they interfere with each other? And where/when?
--
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.