Hello Neil, we have compiled the natty kernel with dynamic debugging enabled for raid456, and reproduced the problem. The kernel log is available at https://docs.google.com/open?id=0B9rmyUifdvMLMzk1YjYwZDUtYzhhYi00MDRlLTkzYjItMDM0Y2ZhZmU3ZDRk Some more information: - array was created at Nov 27 11:28:03 - manual drive failure was issued at 11:28:09 Please let me know if you need any additional information. Thanks for your help, Alex. > The fact that md1123_raid5 is spinning suggest there is one request that > is being handled over and over again - each time handle_stripe5 thinks that > it cannot handle it yet, but leaves it in a state which indicates that it > still needs handling. > However I cannot see how that could possible happen. > > If your kernel had dynamic debugging enabled we could turn that on for RAID5 > and see a bit more of what is happening. > i.e. > echo module raid456 > /sys/kernel/debug/dynamic_debug/control > > with the debug filesystem mounted on /sys/kernel/debug > > However that Ubuntu kernel doesn't have CONFIG_DYNAMIC_DEBUG set so you > would need to compile a new kernel. > > I cannot think of any other way forward with this. > > BTW when I tested your script on the very latest kernel I hit a completely > unrelated bug what was introduced very recently which I can now fix. So I'm > particularly glad that I looked at this :-) > > NeilBrown > > -- 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
