diff options
| author | NeilBrown <neilb@suse.de> | 2009-12-13 20:49:49 -0500 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2009-12-13 20:49:49 -0500 |
| commit | efa593390e70b0e3c39f6b2dca8876b6b1461e41 (patch) | |
| tree | 99c6071381f14f5ff59130779d988672aa78ee67 /drivers/md/raid0.c | |
| parent | c07b70ad32ed0a5ec9735cafb1aa10b3a2298b7d (diff) | |
md: don't reset curr_resync_completed after an interrupted resync
If a resync/recovery/check/repair is interrupted for some reason, it
can be useful to know exactly where it got up to.
So in that case, do not clear curr_resync_completed.
Initialise it when starting a resync/recovery/... instead.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid0.c')
0 files changed, 0 insertions, 0 deletions