summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.com>2015-07-24 03:27:08 (GMT)
committerNeilBrown <neilb@suse.com>2015-08-31 17:38:17 (GMT)
commit5ed1df2eacc0ba92c8c7e2499c97594b5ef928a8 (patch)
treed712ddbdc3bfcbc710f6823076691e96f197baf7 /COPYING
parentc5e19d906a658f27fa858b09a95d9551b1a69bd0 (diff)
downloadlinux-5ed1df2eacc0ba92c8c7e2499c97594b5ef928a8.tar.xz
md: sync sync_completed has correct value as recovery finishes.
There can be a small window between the moment that recovery actually writes the last block and the time when various sysfs and /proc/mdstat attributes report that it has finished. During this time, 'sync_completed' can have the wrong value. This can confuse monitoring software. So: - don't set curr_resync_completed beyond the end of the devices, - set it correctly when resync/recovery has completed. Signed-off-by: NeilBrown <neilb@suse.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions