It prints out: Kernel md module does not support events. and immediately exits.
Needs the updated kernel md code. I was told by Neil Brown that he was going to push that into 2.6 himself. Will have to check with him. Regardless though, it's a kernel issue, not an mdmpd issue.
*** Bug 119834 has been marked as a duplicate of this bug. ***
*** Bug 121243 has been marked as a duplicate of this bug. ***
*** Bug 121832 has been marked as a duplicate of this bug. ***
Did this get pushed in? If not, we should disable mdmpd.
I still see "mdmpd failed" at startup on x86_64 with no software raid (was everything install). No other messages. This may be a different problem.
*** Bug 122691 has been marked as a duplicate of this bug. ***
I've contacted the md maintainer to get a 2.6 version of the event interface patch. No word back yet. I'll rebuild a new package today that doesn't turn the program on by default.
The upstream md maintainer is going to try and push the event interface into the mainstream kernel in about a week.
Created attachment 100940 [details] MD Event interface patch This is the patch that implements the md event interface. It's currently the only outstanding md patch that the upstream maintainer has not yet submitted to the 2.6 kernel.
Problem still present with current kernel-2.6.6-1.435.2.3 Any plans when the patch will be integrated?
Problem still present with current kernel-2.6.7-1.494.2.2
Problem still present with current kernel-2.6.8.1-521 (Fedora Core 2)
The mdadm tools package was modified to work without the md event interface. If it is accepted upstream (which I believe it has been as of 2.6.10-rc1) then we will eventually get it in the future. Since it's an optimization and not a hard requirement for operability (due to the mdadm package update, prior to that it was a hard requirement), I'm closing this bug out as UPSTREAM.