Comment 3 for bug 1548009

Revision history for this message
Colin Ian King (colin-king) wrote :

Thanks Richard,

Just a few things:

"The meat of it is the scrub script I've been using (and recommending in my HOWTO) for years, which scrubs all *healthy* pools. If a pool is not healthy, scrubbing it is bad for two reasons:

1) It adds a lot of disk load which could lead to another failure. We should save that disk load for resilvering.
2) Performance is already less on a degraded pool and scrubbing will make that worse."

Yep, this sounds perfectly reasonable to me.

1) So, how much extra wear will scrubbing involve? I'm concerned that extra write cycles may add extra wear to users using SSDs.
2) How much extra load and performance loss do we get with scrubbing? It would be good to get some idea so we have an informed idea of the kind of impact this adds.

Secondly, this is actually a feature, so if we go with this I need to fix this issue with a feature freeze exception, which requires some extra work.