Ok, after more testing, this lockup happens consistently when bitmaps are switched on and never when they are switched off. Ideas anybody? On Sun, Oct 08, 2006 at 12:25:46AM +0100, Chris Allen wrote: > > > Neil Brown wrote: > >On Tuesday June 13, davidsen@xxxxxxx wrote: > > > >>Will that fix be in 2.6.17? > >> > >> > > > >Probably not. We have had the last 'rc' twice and I so I don't think > >it is appropriate to submit the patch at this stage. > >I probably will submit it for an early 2.6.17.x. and for 2.6.16.y. > > > > > > > > What is the status of this? > > I've been experiencing exactly the same get_active_stripe lockup > on a FC5 2.6.17-1.2187_FC5smp stock kernel. Curiously we have ten > similar heavily loaded > servers but only one of them experiences the problem. The problem > happens consistently after 24 hours or so > when I hammer the raid5 array over NFS, but I've never managed to > trigger it with local access. I'd also > say (anecdotally) that it only started happening since I added a bitmap > to my array. > > > As with the other poster, the lockup is released by increasing > stripe_cache_size. > > > > > > - > 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 - 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
