| commit | 5e8651060cea6b44844521ddcac665e2c021f5d8 | |
| author | NeilBrown <neilb@suse.de> | |
| Thu, 12 Nov 2009 01:08:04 +0000 (12 12:08 +1100) | ||
| committer | NeilBrown <neilb@suse.de> | |
| Thu, 12 Nov 2009 01:08:04 +0000 (12 12:08 +1100) | ||
| tree | 56a2a3de85fae3f7e210c54a9cda305b0341c334 | treesnapshot (tar.gz zip) |
| parent | 8dee7211467a56b7eb4e4359efb0aa4a72e1b6f3 | commitdiff |
md: factor out updating of 'recovery_offset'.
Each device has its own 'recovery_offset' showing how far
recovery has progressed on the device.
As the only real significance of this is that fact that it can
be stored in the metadata and recovered at restart, and as
only 1.x metadata can do this, we were only updating
'recovery_offset' to 'curr_resync_completed' when updating
v1.x metadata.
But this is wrong, and we will shortly make limited use of this
field in v0.90 metadata.
So move the update into common code.
Signed-off-by: NeilBrown <neilb@suse.de>
Each device has its own 'recovery_offset' showing how far
recovery has progressed on the device.
As the only real significance of this is that fact that it can
be stored in the metadata and recovered at restart, and as
only 1.x metadata can do this, we were only updating
'recovery_offset' to 'curr_resync_completed' when updating
v1.x metadata.
But this is wrong, and we will shortly make limited use of this
field in v0.90 metadata.
So move the update into common code.
Signed-off-by: NeilBrown <neilb@suse.de>
| drivers/md/md.c | diffblobblamehistory |