this post was submitted on 28 Nov 2023
1 points (100.0% liked)
Data Hoarder
3 readers
1 users here now
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would be impossible to guess without a knowledge of internal working of a particular SSD. For a NAND-specific file system I've implemented (not SSD but a device using raw SLC NAND) there was a block refresh immediately after ECC error detection at read and also background process checking slowly all the pages in use (one week for a full cycle). Background scan was starting each time after powering on from a randomized point.
Make sense. I guess leaving it idle for some time should be part of the routine. Then again, there's a limit to how far one can go. If the routine ended up being "power up the drive and use it actively for 4 weeks at least" it would just become too much.
I wish there was just a simple feature to click and a progress bar showing that just did this without us having to try figuring things out.