For cluster raid1, we found some issues and some codes need to be improved during the past months, and all the patches are based on for-next branch of md tree. The patchset also available in github as follows: https://github.com/GuoqingJiang/linux/tree/md-for-next Thanks, Guoqing Guoqing Jiang (13): md-cluster: change resync lock from asynchronous to synchronous md-cluser: make resync_finish only called after pers->sync_request md-cluster: wake up thread to continue recovery md-cluster: unregister thread if err happened md-cluster: fix locking when node joins cluster during message broadcast md-cluster: change array_sectors and update size are not supported md-cluster: wakeup thread if activated a spare disk md: set MD_CHANGE_PENDING in a spinlocked region md-cluster: always setup in-memory bitmap md-cluster: sync bitmap when node received RESYNCING msg md-cluster/bitmap: fix wrong calcuation of offset md-cluster/bitmap: fix wrong page num in bitmap_file_clear_bit and bitmap_file_set_bit md-cluster/bitmap: unplug bitmap to sync dirty pages to disk Documentation/md-cluster.txt | 6 +++ drivers/md/bitmap.c | 108 ++++++++++++++++++++++++++++++++++--------- drivers/md/bitmap.h | 3 ++ drivers/md/md-cluster.c | 53 +++++++++++++++++---- drivers/md/md.c | 80 ++++++++++++++++++++++---------- drivers/md/raid1.c | 2 + drivers/md/raid10.c | 6 ++- drivers/md/raid5-cache.c | 2 + drivers/md/raid5.c | 2 + 9 files changed, 207 insertions(+), 55 deletions(-) -- 2.6.6 -- 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
