diff options
author | NeilBrown <neilb@suse.de> | 2009-12-14 01:50:06 (GMT) |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-12-14 01:51:41 (GMT) |
commit | 93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4 (patch) | |
tree | 56006efccad176da1b806978faf60d77c817e6ac /fs/coda | |
parent | aa98aa31987ad9831711ae71ea2270228ab62532 (diff) | |
download | linux-93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4.tar.xz |
md: integrate spares into array at earliest opportunity.
As v1.x metadata can record that a member of the array is
not completely recovered, it make sense to record that a
spare has become a regular member of the array at the earliest
opportunity.
So remove the tests on "recovery_offset > 0" in super_1_sync
as they really aren't needed, and schedule a metadata update
immediately after adding spares to a degraded array.
This means that if a crash happens immediately after a recovery
starts, the new device will be included in the array and recovery will
continue from wherever it was up to. Previously this didn't happen
unless recovery was at least 1/16 of the way through.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'fs/coda')
0 files changed, 0 insertions, 0 deletions