Hmm... That's interesting. Is there a CPU usage threshold before the filer becomes "Busy"? Is it 60%, 70% or what?
Peter Tran
-----Original Message----- From: Larry Rosenman-CyberRamp System Administration [mailto:ler@cyberramp.net] Sent: Tuesday, October 27, 1998 11:22 AM To: quinlan@transmeta.com; Dave Cole Cc: toasters@mathworks.com Subject: RE: raid scrubbing and hot spares
NetApp told me that a "Busy" box will skip Raid Scrub.
I've got a F520 that does the same thing.
I added a rsh to my crontab to force it:
05 03 * * 0 /usr/bin/rsh <HostName> disk scrub start
Larry Rosenman -- Larry Rosenman, Sr. System Administrator, CyberRamp Internet Services E-Mail: ler@cyberramp.net, http://www.cyberramp.net Voice: (214) 343-3333/(817) 461-8484 (Metro)/Fax: (214) 343-3727 Technical Support: (214) 340-2020/(817) 226-2020 (Metro) U.S. Mail: 11350 Hillguard Rd, Dallas, TX 75243-8311
-----Original Message----- From: Daniel Quinlan [mailto:quinlan@transmeta.com] Sent: Tuesday, October 27, 1998 11:10 AM To: Dave Cole Cc: toasters@mathworks.com Subject: Re: raid scrubbing and hot spares
Dave Cole dacole@netcom.ca writes:
We have a number of f230's here that seem to have either stopped doing their raid scrubbing or isn't bothering to report it any more.
One thing that can cause scrubs to be missed sometimes is setting the system time (via rdate) near the top of the hour. If it's not that, I suggest mailing support@netapp.com about it.
- Dan