John Robinson wrote:
On 27/01/2009 05:16, Neil Brown wrote:
[...]
Probably the only practical data structure for this would be a bitmap
similar to the current write-intent bitmap.
Is it really worth supporting this in raid5? Are the sorts of
devices that will benefit from 'discard' requests likely to be used
inside an md/raid5 array I wonder....
Assuming I've understood correctly, this usage map sounds to me like a
useful thing to have for all RAIDs. When building the array in the
first place, the initial sync is just writing a usage map saying it's
all empty. Filesystem writes and discards update it appropriately.
Then when we get failing sectors reported via e.g. SMART or a scrub
operation we know whether they're on used or unused areas so whether
it's worth attempting recovery.
It would seem that this could really speed initialization. A per-stripe
"unused" bitmap could save a lot of time in init, but also in the check
operation on partially used media. It's not just being nice to SDD, but
being nice to power consumption, performance impact, rebuild time...
other than the initial coding and testing required, I can't see any
downside to this.
--
Bill Davidsen <davidsen@xxxxxxx>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
