On Wed, Mar 8, 2017 at 3:32 PM, Gandalf Corvotempesta
<gandalf.corvotempesta@xxxxxxxxx> wrote:
>> The last resort is to remove the broken drive and then replace it - this is
>> likely to trigger further failures and bring down the array.
>
> Why ? I've removed many, many, many disks before with no issue.
> Why removing a disk should bring the whole array down? This seems a bug to me.
In a perfect world where you do scrubbing and your timeouts are
properly configured and your other disks are all in good shape, you're
right. In the real world where people often don't do what, where
multiple bad sectors accumulate on multiple disks before you get a
failure, or where you're just unlucky, a rebuild triggered by removing
a bad disk and adding back a new one has a fair chance of experiencing
a failure during the rebuild.
If you've lost all redundancy due to a disk failure and while doing a
rebuild you experience another read failure or a second disk failure,
whether due to negligence or bad luck, you can lose the whole array.
If you have the option of doing so, therefore, better to --replace
while you still have redundancy.
Eddie
--
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
