diff options
author | 2014-01-14 15:55:14 +1100 | |
---|---|---|
committer | 2014-01-14 16:44:21 +1100 | |
commit | 7eb418851f3278de67126ea0c427641ab4792c57 (patch) | |
tree | 6faa679f307ec0d333765bc87baa50021ebd9959 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | md: Change handling of save_raid_disk and metadata update during recovery. (diff) | |
download | linux-dev-7eb418851f3278de67126ea0c427641ab4792c57.tar.xz linux-dev-7eb418851f3278de67126ea0c427641ab4792c57.zip |
md: allow a partially recovered device to be hot-added to an array.
When adding a new device into an array it is normally important to
clear any stale data from ->recovery_offset else the new device may
not be recovered properly.
However when re-adding a device which is known to be nearly in-sync,
this is not needed and can be detrimental. The (bitmap-based)
resync will still happen, and further recovery is only needed from
where-ever it was already up to.
So if save_raid_disk is set, signifying a re-add, don't clear
->recovery_offset.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions