Am 02.02.2018 um 12:32 schrieb David Brown:
Okay, it would knacker performance a bit, but where you've got a nested
raid like this, you switch it on, run a read on the filesystem ( tar /
--no-follow > /dev/null sort of thing), and it would sort out integrity
all the way down the stack.
That's a scrub. You do it as a very low priority task on a regular basis
if only that "low priority" would work these days....
dev.raid.speed_limit_min = 25000
dev.raid.speed_limit_max = 1000000
in the good old days "dev.raid.speed_limit_max" was how it is named and
when you used your machine the scrub simply took longer, these days (for
many months, few years) you better limit "dev.raid.speed_limit_max" and
type "sysctl -p" and *after* that you can continue to use your machine
--
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
