Chris Thompson wrote:
Adam.Fox@netapp.com writes:
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.
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 "raid scrub stop" command?
hold on chris, i will verify it.
Hannes Herret hh@bacher.at originally wrote
normally the disk scrub starts on sunday 1 a.m. cause of the running ndmp-backup, the filer couldn't finish the scrub within the default deadline time of 6 h.
and it seems to me that a sensible thing to do would be to interrupt the scrub if it hasn't finished by the time the backups start, rather than let them madly compete with each other for disk bandwidth.
it was a misinformation, there is no ndmp-backup running on sunday!! it seems to be normal, to take 10 hours to scrub 2x 19 x 36Gb-Disks.
but another question comes up: this conifg is an f820-cluster. how the clusternodes handles the scrubing? each node scrubs both loops? maybe this is the reason for the long scrub time.
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.