Peter Rabbitson wrote:
I was actually specifically advocating that md must _not_ do anything
on its own. Just provide the hooks to get information (what is the
current stripe state) and update information (the described repair
extension). The logic that you are describing can live only in an
external app, it has no place in-kernel.
So you advocate the current code being in the kernel, which absent a
hardware error makes blind assumptions about which data is valid and
which is not and in all cases hides the problem, instead of the code I
proposed, which in some cases will be able to avoid action which is
provably wrong and never be less likely to do the wrong thing than the
current code?
Currently the "repair" action (which *is* in the kernel now) takes no
advantage of the additional information available in these cases I
noted. By what logic do you conclude that the user meant "hide the
error" when using the "repair" action? What I propose is never less
likely to be correct than what the current code does, why would you not
want to improve the chances of getting the repair correct?
--
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-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
