Messages in this thread Patch in this message | | | From | NeilBrown <> | Date | Tue, 27 Jun 2006 17:05:10 +1000 | Subject | [PATCH 001 of 12] md: Possible fix for unplug problem |
| |
I have reports of a problem with raid5 which turns out to be because the raid5 device gets stuck in a 'plugged' state. This shouldn't be able to happen as 3msec after it gets plugged it should get unplugged. However it happens none-the-less. This patch fixes the problem and is a reasonable thing to do, though it might hurt performance slightly in some cases.
Until I can find the real problem, we should probably have this workaround in place.
Signed-off-by: Neil Brown <neilb@suse.de>
### Diffstat output ./drivers/md/raid5.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff .prev/drivers/md/raid5.c ./drivers/md/raid5.c --- .prev/drivers/md/raid5.c 2006-06-27 12:15:17.000000000 +1000 +++ ./drivers/md/raid5.c 2006-06-27 12:16:41.000000000 +1000 @@ -271,7 +271,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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |