Paul Clements wrote: > Have you been able to reproduce this problem with any regularity? Or > have you tried? I have an idea what *might* be causing this, if you're > willing to try out a patch... Please post it even if he can't try it. All I have found so far is two missing newlines in the status message code (symptom: lines containing "<6>" in the syslog.) (later) just noticed that the raid1 status printout doesn't show the write_only flag. This should probably be added... > BTW, the md "BUG" you originally reported is not really a bug -- that > always happens when you try to raidhotremove an active disk. It calls MD_BUG() when that happens, though. -- Chuck I am not a number! - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
