On 16 May 2017, Phil Turmel spake thusly: > On 05/16/2017 10:53 AM, Wols Lists wrote: >> First thing we do is read the entire stripe. > > A substantial performance degradation, right out of the gate... I'm fairly sure Wol's intention is to do this as part of a check/repair operation. You don't want to run like this in normal usage! (Though I agree that it seems unclear whether you want to do this at all.) However, the existence of raid6check, which is new enough that I'd not noticed it (not being installed by default doesn't help there, as does the lack of mention of autorepair mode in the manpage), makes this entire conversation/argument moot, as far as I can see. If you're really concerned, stick raid6check in early userspace, like mdadm, so you can recover from *anything*. :) The requirement to run raid6check by hand is no more annoying than the requirement to run scrubs by hand: userspace is clearly a better place for this sort of rare obscurity than the kernel, though it's a minor shame raid6check can't tell md that the block device has changed so you wouldn't need to impair availability by taking the array down after fixing things. (Still, this is likely to be needed so rarely that it's completely unimportant.) -- NULL && (void) -- 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
