diff options
| author | Guoqing Jiang <gqjiang@suse.com> | 2016-05-02 11:33:09 -0400 |
|---|---|---|
| committer | Shaohua Li <shli@fb.com> | 2016-05-04 12:39:35 -0700 |
| commit | 2c97cf138527a0f0283fcca9acf4a06216bec7da (patch) | |
| tree | 05b750aa450372d1bf7b2dff81c7293479f01cc7 | |
| parent | 41a9a0dcf8954654467f979838938e39ef4da590 (diff) | |
md-cluser: make resync_finish only called after pers->sync_request
It is not reasonable that cluster raid to release resync
lock before the last pers->sync_request has finished.
As the metadata will be changed when node performs resync,
we need to inform other nodes to update metadata, so the
MD_CHANGE_PENDING flag is set before finish resync.
Then metadata_update_finish is move ahead to ensure that
METADATA_UPDATED msg is sent before finish resync, and
metadata_update_start need to be run after "repeat:" label
accordingly.
Reviewed-by: NeilBrown <neilb@suse.com>
Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
Signed-off-by: Shaohua Li <shli@fb.com>