On 04/11/15 12:05, o1bigtenor wrote:
On Tue, Nov 3, 2015 at 10:01 PM, o1bigtenor <o1bigtenor@xxxxxxxxx> wrote:
On Tue, Nov 3, 2015 at 10:08 AM, Phil Turmel <philip@xxxxxxxxxx> wrote:
One caveat -- don't do this part until you've corrected your timeout mismatch
problem, or any latent UREs will break your array again.
Read through the references.
How do I do what you suggest?
Here's how I do it. This script is run on every bootup.
It iterates through all the drives and uses smartctl to try and set erc
timeouts. If that fails it assumes the drive does not support it and it
sets the timeout value to 180 seconds.
#!/bin/bash
for i in /dev/sd? ; do
if smartctl -l scterc,70,70 $i > /dev/null ; then
echo -n $i " is good "
else
echo 180 > /sys/block/${i/\/dev\/}/device/timeout
echo -n $i " is bad "
fi;
smartctl -i $i | egrep "(Device Model|Product:)"
blockdev --setra 1024 $i
done
I have a mix of 15k SAS drives, WD green & red and some left over bits
and pieces. This ensures the timeouts all match the drives capability.
Regards,
Brad
--
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
