md: Use ->curr_resync as last completed request when cleanly aborting resync.

If a resync is aborted cleanly, ->curr_resync is a reliable
record of where we got up to.
If there was an error it is less reliable but we always know that
->curr_resync_completed is safe.

So add a flag MD_RECOVERY_ERROR to differentiate between these cases
and set recovery_cp accordingly.

Signed-off-by: Jianpeng Ma <majianpeng@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>

1 files changed, 2 insertions, 0 deletions

diff --git a/drivers/md/md.h b/drivers/md/md.h
index af443ab868db..c29e62ebc488 100644
--- a/drivers/md/md.h
+++ b/drivers/md/md.h
@@ -307,6 +307,7 @@ struct mddev {
          * REQUEST:  user-space has requested a sync (used with SYNC)
          * CHECK:    user-space request for check-only, no repair
          * RESHAPE:  A reshape is happening
+         * ERROR:    sync-action interrupted because io-error
          *
          * If neither SYNC or RESHAPE are set, then it is a recovery.
          */
@@ -320,6 +321,7 @@ struct mddev {
 #define MD_RECOVERY_CHECK       7
 #define MD_RECOVERY_RESHAPE     8
 #define MD_RECOVERY_FROZEN      9
+#define MD_RECOVERY_ERROR       10
 
         unsigned long                   recovery;
         /* If a RAID personality determines that recovery (of a particular