On Wednesday, January 11, 2023 12:20:05 PM Linux-Fan wrote: > > Or does one need to read every byte, allocated or not? > > AFAIK one needs to _power_ the device every once in a while and keep power > connected for some time. Then, the controller can dos all the necessary > actions in the background.
... > Here is an article from 2021 that shows some typical numbersas I > remembered them. I do not know anything about this specific source's > credibility, though: > https://www.virtium.com/knowledge-base/ssd-data-retention/ > > This entry seems to be rather pessimistic: > https://www.ibm.com/support/pages/potential-ssd-data-loss-after-extended-sh > utdown I've read some of that article, or, I guess, really the abstract and the section labeled "Content" on that page: https://www.ibm.com/support/pages/potential-ssd-data-loss-after-extended- shutdown I see the statement: "A system (and its enclosed drives) should be powered up at least 2 weeks after 2 months of system power off. If a drive has an error indicating it is at end of life we recommend not powering off the system for extended periods of time.", and the first quoted paragraph in this email reiterates the need to power up occasionally and leave connected for some time (so that the controller can do all the necessary actions in the background). I assume that they are talking about the hardwired controller built into the drive, thus there is no particular need to power it up from an OS that recognizes it but simply something that powers it somehow? Can anyone shed more light on what happens during that two weeks -- is the data somehow "refreshed" (in place), or rewritten somewhere else on the drive, or ??? (Perhaps that is discussed in the complete article of which this appears to be just the abstract??) Thanks! -- rhk (sig revised 20221206) If you reply: snip, snip, and snip again; leave attributions; avoid HTML; avoid top posting; and keep it "on list". (Oxford comma (and semi-colon) included at no charge.) If you revise the topic, change the Subject: line. If you change the topic, start a new thread. Writing is often meant for others to read and understand (legal documents excepted?) -- make it easier for your reader by various means, including liberal use of whitespace (short paragraphs, separated by whitespace / blank lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and references. If someone has already responded to a question, decide whether any response you add will be helpful or not ... A picture is worth a thousand words. A video (or "audio"): not so much -- divide by 10 for each minute of video (or audio) or create a transcript and edit it to 10% of the original. A speaker who uses ahhs, ums, or such may have a real physical or mental disability, or may be showing disrespect for his listeners by not properly preparing in advance and thinking before speaking. (Remember Cicero who did not have enough time to write a short missive.) (That speaker might have been "trained" to do this by being interrupted often if he pauses.) A radio (or TV) station which broadcasts speakers with high pitched voices (or very low pitched / gravelly voices) (which older people might not be able to hear properly) disrespects its listeners. Likewise if it broadcasts extraneous or disturbing sounds (like gunfire or crying), or broadcasts speakers using their native language (with or without an overdubbed translation). A person who writes a sig this long probably has issues and disrespects (and offends) a large number of readers. ;-) '
