The only thing google turned up was "stop the scrub if it impacts performance too badly" which is not really all that helpful. Or ways to speed up scrubs & resilvers.
In my case, I'd like to be able to run a scrub and have all the performance hits taken by the scrub process if the system has other loads. I care that the scrub runs, but not how fast. >From observed behavior, it appears that the scrub is consuming too large a >share of DRAM (12 GB in this case). Is that correct and if so, is there a way >to limit the proportion of memory used by the scrub process? I'd like to be able to schedule scrubs regularly, but the present behavior would require predicting when I didn't want to use the system for work. Thanks, Reg _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
