summaryrefslogtreecommitdiffstats
path: root/include/linux/raid
diff options
context:
space:
mode:
authorNeil Brown <neilb@notabene.brown>2008-06-28 08:31:24 +1000
committerNeil Brown <neilb@notabene.brown>2008-06-28 08:31:24 +1000
commit5e96ee65c8bd629ce093da67a066d3946468298a (patch)
treee1ff9e4984d71ffaa842e7e1d19c282fa9e01bcd /include/linux/raid
parenta0da84f35b25875870270d16b6eccda4884d61a7 (diff)
downloadkernel-crypto-5e96ee65c8bd629ce093da67a066d3946468298a.tar.gz
kernel-crypto-5e96ee65c8bd629ce093da67a066d3946468298a.tar.xz
kernel-crypto-5e96ee65c8bd629ce093da67a066d3946468298a.zip
Allow setting start point for requested check/repair
This makes it possible to just resync a small part of an array. e.g. if a drive reports that it has questionable sectors, a 'repair' of just the region covering those sectors will cause them to be read and, if there is an error, re-written with correct data. Signed-off-by: Neil Brown <neilb@suse.de>
Diffstat (limited to 'include/linux/raid')
-rw-r--r--include/linux/raid/md_k.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/raid/md_k.h b/include/linux/raid/md_k.h
index 3dea9f545c8..780e0613e6d 100644
--- a/include/linux/raid/md_k.h
+++ b/include/linux/raid/md_k.h
@@ -227,6 +227,8 @@ struct mddev_s
atomic_t recovery_active; /* blocks scheduled, but not written */
wait_queue_head_t recovery_wait;
sector_t recovery_cp;
+ sector_t resync_min; /* user requested sync
+ * starts here */
sector_t resync_max; /* resync should pause
* when it gets here */