I'd like to know your use case, can you describe it in details? I thought only
raid6check uses this function. If there are other usage cases which depend on
current behavior, we certaily can't change it.
It's entirely manual. I have a series of test arrays I use when people
come to the list with issues and it's not uncommon to get into sysfs to
manipulate the arrays to either re-create a situation or get the array
into a state where I can try and figure out what is going on. To be
honest all the use cases for me are entirely pathological, but it's a
change to the current behavior that I have used in the past and expect
to use again in the future.
The issue being rectified is not one I've seen come up frequently (if at
all) so I thought I'd pipe up and say "I have used this in the past and
will probably use it again in the future, please don't break it of you
can avoid it".
I am currently 17,600KM away from my test stuff, so I can't elaborate
further at the moment.
Regards,
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
--
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
