[prev in list] [next in list] [prev in thread] [next in thread] 

List:       smartmontools-support
Subject:    [smartmontools-support]smartd - best practice?
From:       "Gary Funck" <gary () intrepid ! com>
Date:       2005-08-23 15:42:09
Message-ID: JCEPIPKHCJGDMPOHDOIGMENEDAAA.gary () intrepid ! com
[Download RAW message or body]

Right now, we run the -H (health test) option via smartd on all our
system disks, which per the manual page tests for changes in
pre-fail attributes that signal an imminent disk failure.  We don't
run self-tests, but I'm thinking that we should.  What is the recommended
interval for running self tests?  Is there any merit in running the
short tests, or should we also run the long tests?




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support
[prev in list] [next in list] [prev in thread] [next in thread]