On Fri, 2 Jun 2006, Neil Brown wrote: > On Friday June 2, dean@xxxxxxxxxx wrote: > > On Thu, 1 Jun 2006, Neil Brown wrote: > > > > > I've got one more long-shot I would like to try first. If you could > > > backout that change to ll_rw_block, and apply this patch instead. > > > Then when it hangs, just cat the stripe_cache_active file and see if > > > that unplugs things or not (cat it a few times). > > > > nope that didn't unstick it... i had to raise stripe_cache_size (from 256 > > to 768... 512 wasn't enough)... > > > > -dean > > Ok, thanks. > I still don't know what is really going on, but I'm 99.9863% sure this > will fix it, and is a reasonable thing to do. > (Yes, I lose a ';'. That is deliberate). it's been running for a week now... and the freeze hasn't occured... it's possible the circumstances for reproducing it haven't occured again either, but i haven't really changed my disk usage behaviour so it's probably fixed. let me know if you come up with some other solution you'd like tested. thanks -dean > > Please let me know what this proves, and thanks again for your > patience. > > NeilBrown > > > Signed-off-by: Neil Brown <neilb@xxxxxxx> > > ### Diffstat output > ./drivers/md/raid5.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff ./drivers/md/raid5.c~current~ ./drivers/md/raid5.c > --- ./drivers/md/raid5.c~current~ 2006-05-28 21:56:56.000000000 +1000 > +++ ./drivers/md/raid5.c 2006-06-02 17:24:07.000000000 +1000 > @@ -285,7 +285,7 @@ static struct stripe_head *get_active_st > < (conf->max_nr_stripes *3/4) > || !conf->inactive_blocked), > conf->device_lock, > - unplug_slaves(conf->mddev); > + raid5_unplug_device(conf->mddev->queue) > ); > conf->inactive_blocked = 0; > } else > - > 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
