Am 14.07.2017 um 00:34 schrieb Gionatan Danti:
Il 13-07-2017 23:34 Reindl Harald ha scritto:
maybe because the disk is, well, not in a good shape and don't know
that by itself
But the kernel *does* know that, as the dmesg entries clearly show.
Basically, some SATA commands timed-out and/or were aborted. As the
kernel reported these erros in dmesg, why do not use these information
to stop a failing disk?
because you won't be that happy when the kernel spits out a disk each
time a random SATA command times out - the 4 RAID10 disks on my
workstation are from 2011 and showed them too several times in the past
while they are just fine
here you go:
http://strugglers.net/~andy/blog/2015/11/09/linux-software-raid-and-drive-timeouts/
--
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
