3 ms·
Because with ZFS bit rot can be cumulative, with most file systems a memory error will corrupt a file if the format can't handle errors, with ZFS overtime the e
by dogma1138 10y ago
Because with ZFS bit rot can be cumulative, with most file systems a memory error will corrupt a file if the format can't handle errors, with ZFS overtime the entire volume can get corrupted especially when you are doing recovery or expansion, even in normal operation data is moved around quite a bit.
For them most part with other common file systems when a file is written it stays there even in RAID.
- Dylan16807 10y agoI don't know, I wouldn't say ZFS moves files around any more than a typical filesystem.
- blackflame7000 10y agoCorrect. ZFS won't do unnecessary file reordering unless a scrub has been initiated.
- wtallis 10y agoThe only detailed explanations I've ever seen for how memory errors can snowball into whole-filesystem loss on ZFS have relied on the assumption that you have a deterministically stuck bit in a region of memory that the OS is re-using for different parts of the FS data structures but never anything that could cause the machine itself to crash (thereby clueing you in to a hardware reliability issue). Do you have a source for a more plausible analysis that takes into account how memory actually tends to fail?