3 ms·
Tesla was having issues with log file writes destroying their chips. They can argue they have precedent for deleting data, but not hiding it.
by 1970-01-01 1y ago
Tesla was having issues with log file writes destroying their chips. They can argue they have precedent for deleting data, but not hiding it.
- Hamuko 1y agoWouldn't creating an archive on the filesystem and then deleting the archive cause more writes than just creating it without a delete?
- potato3732842 1y agoI think the goal is to save as much as you can in the interim. Holding onto X bytes of archives is more time worth of data than X bytes of uncompressed. We do that stuff all the time in finance. Stuff gets spewed off to external places and local copies get kept but archived and we simply rotate the oldest stuff out as we go. If the cleanup process is configured separately from the archiving process you can absolutely archive things just to remove them shortly thereafter.
- 1970-01-01 1y agoWear increases when free space is low as there's less overall space to put the data. If you only have 500MB of free space, those blocks take the majority of write hammering until the chip fails. If there's 5000MB free, you can spread the wear.
- LorenPechtel 1y agoNot in the big picture. Fundamentally, flash memory is a bunch of pages. Each page can be read an infinite number of times but there are quite relevant limits on how many times you can write it. In the simplistic system lets say you have 1000 pages, 999 hold static data and the last one keeps getting a temporary file that is then erased. All wear occurs on page 1000 and it doesn't last very long. In the better system it notes that page 1000 is accumulating a lot of writes and picks whatever page has the least writes, copies the data from that page to page 1000 and now uses the new page for all those writes. Repeat until everything's worn down. Note the extra write incurred copying the page over. In the real world a drive with more space on it is less likely to have to resort to copying pages.
- throwanem 1y agoI would be fascinated to entertain arguments for how the future write life of a flash memory chip, meant for storing drive-time telemetry in a wrecked car, merits care for preservation.
- 1970-01-01 1y agoMany parts, especially non-moving parts, hold value after a wreck. It does not make sense to keep the file on the disk for the lifetime of the part. The part is most likely going to be resold as used. The part will have a shorter life if the big crash data file is left on disk.
- throwanem 1y agoI didn't know Tesla authorized any resale of parts from any of their vehicles, used, crashed, or otherwise! Certainly I had no idea they built support for it into the system software. Was that a recent change?
- 1970-01-01 1y agohttps://Service.tesla.com https://Service.tesla.com has been online for I think 2 years
- throwanem 1y agoOh, I'm sure it has. Owners tell a different story about what the site is worth. Of course, Apple actually "innovated" that one. But do you seriously mean to suggest Tesla engineer their cars to discard potentially dispositive crash analysis, in order to support their own resale of junkyard pulls?
- 1970-01-01 1y agoWhat's the alternative? Keep it on there for the next owner to view?