md-cluster: introduce resync_info_get interface for sanity check
Since the resync region from suspend_info means one node is reshaping this area, so the position of reshape_progress should be included in the area. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com>
This commit is contained in:

committed by
Shaohua Li

parent
7564beda19
commit
5ebaf80bc8
@@ -4785,8 +4785,14 @@ static void end_reshape(struct r10conf *conf)
|
||||
static void raid10_update_reshape_pos(struct mddev *mddev)
|
||||
{
|
||||
struct r10conf *conf = mddev->private;
|
||||
sector_t lo, hi;
|
||||
|
||||
conf->reshape_progress = mddev->reshape_position;
|
||||
md_cluster_ops->resync_info_get(mddev, &lo, &hi);
|
||||
if (((mddev->reshape_position <= hi) && (mddev->reshape_position >= lo))
|
||||
|| mddev->reshape_position == MaxSector)
|
||||
conf->reshape_progress = mddev->reshape_position;
|
||||
else
|
||||
WARN_ON_ONCE(1);
|
||||
}
|
||||
|
||||
static int handle_reshape_read_error(struct mddev *mddev,
|
||||
|
Reference in New Issue
Block a user