hi all,
normally the disk scrub starts on sunday 1 a.m. cause of the running ndmp-backup, the filer counldn't finish the scrub within the default deadline time of 6 h.
there are 4 volumes on the filer and just 1 finished the scrub. the other get stopped like following: Sun Jul 8 01:00:00 CES [fsup02: raid_scrub_admin:notice]: Beginning disk scrubbing... Sun Jul 8 07:00:01 CES [fsup02: consumer:notice]: Disk scrub stopped because the scrub time limit was exceeded. Sun Jul 8 07:00:01 CES [fsup02: consumer:notice]: Scrub for volume vol0, RAID group 0 stopped at stripe 13435506. Sun Jul 8 07:00:01 CES [fsup02: consumer:notice]: 0 new parity inconsistencies found, 0 to date. Sun Jul 8 07:00:01 CES [fsup02: consumer:notice]: 0 new checksum errors found, 0 to date.
how to resolve this?
a. disable automatic disk scrub and start it with cron via rsh i don' like it, cause of the administration b. set the day of the disk scrub to e.g. saturday how to set on the filer? c. lenghten the scrub time limit with raid.scrub.duration i think the default is 0 and the setting works with minutes 0 means unlimited time? 480 means 8 hours? d. optimize scrubbing with raid.scrubbers default is 2 is that the number of processes ontap should use for scrubbing?
a or b or c or d, or all of them?
any other suggestions or comments are welcome !!
cu hannes