2 ms·
Indeed, that was my guess as well given the performance improvements re-writing the data. The facebook study also observes to another potential source for the
by mjevans 11y ago
Indeed, that was my guess as well given the performance improvements re-writing the data. The facebook study also observes to another potential source for the performance variation.
According to the paper on /some/ tested drives the presence of trimmed data (such as through OS updates/etc) could lead to more complicated re-mapping patterns and thus a longer tree search when finding the correct block to read. However that doesn't correlate well with the observed speed at which the backups were reading data over time. The read speed was highly variable; with an extremely slow initial portion that would likely correlate well to stable windows install files.
- cushychicken 11y agodr_zoidberg's reply males a lot of sense - it sounds like you experienced a lot of basic retention and errors, which is reasonably common on modern small process NAND. Since you're executing a block erase at the device level by doing the secure erase operation. It's setting all those pages that leaked charge - and by extension, your data - back to 1s,so they're ready to be written again. I'm a little surprised that the stale time was on the order of a year. Have you experienced any other failures?