On Wednesday December 17, jnelson-linux-raid@xxxxxxxxxxx wrote: > > > >> It could be that you are hitting the bug fixed by > >> commit a0da84f35b25875870270d16b6eccda4884d61a7 > > > > That sure sounds like it. I'd have to log to see what happened, > > exactly, but I've added substantial logging around the device > > discovery and addition section which manages this particular raid. > > > >> You would need 2.6.26 or later to have that fixed. > >> Can you try with a newer kernel??? > > > > I hope to be giving opensuse 11.1 a try soon, which uses 2.6.27.X > > afaik. I suspect I can also backport that patch to 2.6.25 easily. > > The kernel source for 2.6.25.18-0.2 (from suse) has this patch > already, so I was already using it. Are you sure? I just looked in the openSUSE-11.0 kernel tree and I cannot see it there.... NeilBrown > > Perhaps this weekend or some night this week I'll find time to try to > break things again. > > -- > Jon -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
