Adam.Fox@netapp.com wrote:
From the looks of your syslog messages, it appears that you are running 6.x. The good news here is that when the time expires under 6.x, the disk scrub picks up at that point on the next disk scrub. So you may not be scrubbing every sector every week, but you will be scrubbing every sector every 2 or 3 weeks.
and I asked: < < Does this sort of restarting from a checkpoint (presumably the < information in the state.raid.scrub.* entries in /etc/registry) < apply if the scrub was interrupted by a "disk scrub stop" command?
and Hannes Herret hh@bacher.at replied (off-list): | | yes. if you stop a manually initiated disk scrub, the last stripe is | also logged to the registry.
This is certainly true, and the automatic scrub at 01:00 on Sunday will restart from a checkpoint created by "disk scrub stop" - I have tried it.
But there's an infelicity (bug?) in that "disk scrub start" always starts a full scrub starting at the beginning, and ignores any checkpoint left by "disk scrub stop" (or, presumably, by a scrub timeout, although I haven't tested that case). This means that if one wants to run a regular scrub at some other time than the default, one cannot get any advantage from the checkpointing.
This cannot be right, surely? At the very least, there ought to be "disk scrub continue" option that does respect the checkpoint info.
All tests were done with DOT 6.1R1.
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.