On 09/15/2013 07:42 AM, Adam Levin wrote: > > Regarding protecting against corruption, that's the point of the erasure > coding. Mathematically, there can't be any, or at the very least, if > there *is*, it's corrected right away by calculations from the rest of > the data. The data is spread far and wide to protect against disk, > shelf, controller or even site failures (it's a *globally* distributed > filesystem). >
What happens when you run into a bug in the filesystem that trashes data, or miscalculates the erasure coding? One of the advantages of a separate DR system (whether it's disk or tape) is that the likelihood of a bug trashing the same data in two distinct systems is much lower than it is in one system. Skylar _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
