diff options
author | Dan Williams <dan.j.williams@intel.com> | 2010-06-15 18:41:57 -0700 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2010-06-15 18:41:57 -0700 |
commit | 4f0a7acc9a0a93d39b66b29e374f9a5edd173047 (patch) | |
tree | 5d4b7f9ff2453cdaa778b248effdba4354adbd79 /mdadm.8 | |
parent | 0d80bb2f97e876379fb0ba732e8e97894ebe3de9 (diff) | |
download | mdadm-4f0a7acc9a0a93d39b66b29e374f9a5edd173047.tar.gz mdadm-4f0a7acc9a0a93d39b66b29e374f9a5edd173047.tar.xz mdadm-4f0a7acc9a0a93d39b66b29e374f9a5edd173047.zip |
mdmon: record sync_completed directly to the metadata
When sync_action is idle mdmon takes the latest value of md/resync_start
or md/<dev>/recovery_start to record the resync/rebuild checkpoint in
the metadata. However, now that mdmon is reading sync_completed there
is no longer a need to wait for, or force an idle event to take a
checkpoint.
Simply update the forward progress of ->last_checkpoint at every wakeup
event and force it to be recorded at least every 1/16th array-size
interval. It may be recorded more frequently if a ->set_array_state()
event occurs.
This also cleans up some confusion in handling the dual-rebuild case.
If more than one spare has been activated the kernel starts the rebuild
at the lowest recovery offset, so we do not need to worry about
min_recovery_start().
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'mdadm.8')
0 files changed, 0 insertions, 0 deletions