Hello! On Tue, Feb 8, 2011 at 3:25 AM, NeilBrown <neilb@xxxxxxx> wrote: [snip] > Then start either the > 'next' array at the beginning, or the 'current' array at the current point > (write to sync_min). I couldn't find documentation for sync_min/sync_max sysfs params at least for repo cloned from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.37.y.git coolcold@coolcold:~/gits/linux-2.6.37.y$ grep -qi sync_min Documentation/md.txt || echo failed find docs failed find docs As I could understand from sources - resync_min & resync_max are expressed in sectors (512bytes?) and are set to 0 & total sectors on device accordingly. resync_max value should be divisible by array chunk size (in sectors) . After setting this values, one can trugger "check" / "repair" into sync_action. My basic idea is to use this method to clear pending sectors from SMART checks and looks like this gonna work, am i right? > Then wait for however long you want, abort the check (write 'idle' to > 'sync_action') and find out where it got up to (read sync_min) and record > that for next time. > > NeilBrown > -- Best regards, [COOLCOLD-RIPN] -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
