diff options
| author | Guoqing Jiang <gqjiang@suse.com> | 2016-05-02 11:50:11 -0400 |
|---|---|---|
| committer | Shaohua Li <shli@fb.com> | 2016-05-04 12:39:35 -0700 |
| commit | c9d65032282943d11b2773ed6f0279ba4820fed1 (patch) | |
| tree | dac5992b197795b439209d79c5717ad1af76e3f5 | |
| parent | a578183ed9dff915878ec6c2b3bf729bf72b9bd1 (diff) | |
md-cluster: always setup in-memory bitmap
The in-memory bitmap for raid is allocated on demand,
then for cluster scenario, it is possible that slave
node which received RESYNCING message doesn't have the
in-memory bitmap when master node is perform resyncing,
so we can't make bitmap is match up well among each
nodes.
So for cluster scenario, we need always preserve the
bitmap, and ensure the page will not be freed. And a
no_hijack flag is introduced to both bitmap_checkpage
and bitmap_get_counter, which makes cluster raid returns
fail once allocate failed.
And the next patch is relied on this change since it
keeps sync bitmap among each nodes during resyncing
stage.
Reviewed-by: NeilBrown <neilb@suse.com>
Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
Signed-off-by: Shaohua Li <shli@fb.com>