Am 09.05.2017 um 13:15 schrieb Nix:
On 9 May 2017, Reindl Harald said:
Am 09.05.2017 um 12:28 schrieb Nix:
Honestly, scrubs are looking less and less desirable the more I talk
about them. Massive worry inducers that don't actually spot problems in
any meaningful sense (not even at the level of "there is a problem on
this disk", just "there is a problem on this array")
that is your opinion
my expierience over years using md-arrays is that *everytime* smartd triggered a alert mail that a drive will fail soon it happened
while the scrub was running and so you can replace drives as soon as possible
What, it triggered a SMART warning while a scrub was running which SMART
long self-tests didn't? That's depressing. You'd think SMART would be
watching for errors while it's own tests were running!
different time of tests, different access metrics
i guess smarter people like both of us had a reason to develop scrub
instead say "just let the drive do it at it's own
(Or were you not running any long self-tests? That's at least as risky
as not scrubbing, IMNSHO.)
no i do both regulary
* smart short self-test daily
* smart long self-test weekly
* raid scrub weekly
and no - doing a long-smart-test daily is not a good solution, the
RAID10 array in my office makes *terrible noises* when the SMART test is
running and after doing this every week the last 6 years (Power_On_Hours
14786, Start_Stop_Count 1597) i would say they are normal but probably
it's not good doing that operations all the time
well, that machine has not lost a single drive, a clone of it acting as
homeserver 365/24/7 has lost a dozen in the same time....
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
