On 02/02/18 11:32, David Brown wrote: > You already do that during a scrub. You don't want to do it during > normal operations - unless you have a usage pattern with mostly big > reads, you will cripple performance. A small performance drop is > acceptable if it can be shown to significantly improve reliability - but > making every read a full stripe read will give you random read > performance closer to that of a single disk than a raid array. Unless integrity is more important than speed? Unless (like in your own example) you know there's a problem and you want to find it? Yup I know it will knacker performance - I said so. But there are plenty of use cases where it would actually be very useful, and probably the lesser of two evils. (Actually, re-reading your original email, it actually sounds like the right thing to do would be to call hdparm to mark the sector bad on sda, rather than use badblocks, so it will rewrite and clear itself. And this is also a perfect example of where my technique would be useful - it's probably not the raid-5 parity block that gets corrupted, therefore the data itself has been corrupted, therefore my utility would find the damaged file for you so you could recover from backup. A scrub at the raid-5 level would just "fix" the parity and leave you with a corrupted file waiting to blow up on you.) Cheers, Wol -- 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
