diff options
| author | NeilBrown <neilb@suse.de> | 2012-10-11 05:25:57 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2012-10-11 05:25:57 +0200 |
| commit | 72f36d5972a166197036c1281963f6863c429bf2 (patch) | |
| tree | 9bf42eb456ea85126489dad2283ed0343d91172d /Documentation | |
| parent | md/raid5: be careful not to resize_stripes too big. (diff) | |
| download | linux-72f36d5972a166197036c1281963f6863c429bf2.tar.xz linux-72f36d5972a166197036c1281963f6863c429bf2.zip | |
md: refine reporting of resync/reshape delays.
If 'resync_max' is set to 0 (as is often done when starting a
reshape, so the mdadm can remain in control during a sensitive
period), and if the reshape request is initially delayed because
another array using the same array is resyncing or reshaping etc,
when user-space cannot easily tell when the delay changes from being
due to a conflicting reshape, to being due to resync_max = 0.
So introduce a new state: (curr_resync == 3) to reflect this, make
sure it is visible both via /proc/mdstat and via the "sync_completed"
sysfs attribute, and ensure that the event transition from one delay
state to the other is properly notified.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions