|
|
|
|
|
|
by myself248
832 days ago
|
|
|
Thank you, that's helpful! > in other words as you interleave more and more blocks, you get a maximal burst size closer and closer to the size of your total number of parity fragments. I think this could be called out more clearly, as my default assumption was this limit case -- the file grows by X amount, I can recover from up to X amount of corruption. It sounds like that's only the case if the interleave is set to maximum, which is not the default. Is that because, as you increase the interleave, it increases the amount of the stream you need to read in order to repair any corruption? |
|
|
Yes, as you need to read the entire set of interleaved blocks to get each respective block, so to keep memory consumption low, we don't want to interleave too many blocks. I could increase the default to something higher though.
Regarding the tape problem, I was being a bit daft in my response, as if you lose a chunk of tape, you also lose some indeterminate number of data with it, which my format currently isn't capable of recovering from. I'll try to fix that to some degree in the next version, at the cost of not guaranteeing backwards compatibility as I feel it falls under that major problem comment I made in the v0.1 release.