From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: problem formatting new 256 GB USB stick : glances at gparted
Date: Sun, 09 Mar 2025 10:31:19 +0000 [thread overview]
Message-ID: <6031675.MhkbZ0Pkbq@rogueboard> (raw)
In-Reply-To: <35c4444d-446e-d9ca-7ead-8129c0d77595@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4786 bytes --]
On Saturday, 8 March 2025 22:48:29 Greenwich Mean Time Dale wrote:
> Frank Steinmetzger wrote:
> > Am Thu, Feb 20, 2025 at 11:40:48PM +0100 schrieb Frank Steinmetzger:
> >> Another thing to consider: don’t put it into the safe for a year without
> >> powering it up. As was explained in a previous mail, QLC uses sixteen
> >> different levels of charge inside one single flash cell. The chance of a
> >> bit flip increases the longer the SSD is powerless and charge slowly
> >> (very slowly) dissipates. It’s hard to find exact numbers, and it’s more
> >> of a statistical question. Could be a research topic for a slow Sunday.
> >> ;-) Also, don’t you live in a hot area?
> >
> > I knew I’ve seen this data in the past, but couldn’t remeber where and in
> > what context. I just stumbled upon the relevant info again.
> >
> > If you search for "jedec temperature and data retention" you find this
> > PDF:
> > https://www.jedec.org/sites/default/files/Alvin_Cox%20%5BCompatibility%20M
> > ode%5D_0.pdf
> >
> > It contains establised standard values for flash durability. On slide 28
> > it
> > says:
> > Client-class SSDs should retain their data w/o power for 1 year if used
> > 8 hours/day at 40 °C and kept at or below 30 °C when off.
> > There is also a table for other temperatures; the time is cut in half for
> > 5 degrees more.
> >
> > Mind you, that PDF is 15 years old, TLS had just been released to the
> > public one year earlier according to
> > https://en.wikipedia.org/wiki/Multi-level_cell#Triple-level_cell
> >
> > -- Grüße | Greetings | Salut | Qapla’ Please do not share anything
> > from, with or about me on any social network. Some are so convinced,
> > they don’t even know anymore of what.
>
> That is confusing. Data should be OK for one year without power but
> only if powered 8 hours per day. Me scratches my head. Maybe it means
> should be OK for a year without power and not sure what to think about
> rest.
As I understand it these are two different performance requirements, which
were stipulated in this proposed standard back in 2010.
The first, "Active Use (power on)", describes the level of performance on a
typical client workload and operating environment, 8hrs/day at 40°C. I don't
know if this is controller temperature, NAND flash cell temperature, device
sensor temperature, PC case temperature, or room temperature. The actual
standard document would explain this, as well as the method for measuring it.
Meanwhile, I note my NVMe SSD's sensor tells me the drive is idling at 45.8°C
as I write this. o_O
The second, "Retention Use (power off)", sets a limit of 1 year @30°C.
The FFR and UBER thresholds apply to *both* of the above.
> I suspect that things have changed a lot in that time frame despite the
> confusion. They may have improved things significantly since then.
Hmm ... I wouldn't take this to the bank. Standards are typically formulated
following consultation with industry to establish the art of the possible, but
without cutting too much slack on manufacturers so as to promote innovation
and improvement. The manufacturers seek to minimise overall costs, while
keeping their head above the thresholds stated in the standard. So there's a
tension right there, which hopefully delivers innovation and ideally lowers
costs over time - but it does not necessarily improve performance. Check how
quality of USB flash drives has gone south over the years, following the
trajectory of their price.
The move from SLC to QLC has been effective in reducing costs, but at some
point the limits of physics will constrain performance. It would be
interesting to dig out the latest JEDEC standard and compare thresholds to see
how they may have improved with more modern manufacturing methods.
> Still, if the one year part, less the other part, is accurate then but
> better now, then my powering up even once a month should be OK. I only
> need to worry about if something happens to me and no one touches it for
> many months, a year or longer.
Given the temperature of the device would probably be below 30°C for at least
half of the year in day time and most nights, I would think your data will be
fine. :-)
I have a 11 year old Toshiba OCZ SSD, which gave me a scare a week ago. It
reported an I/O error, dmesg showed it being inaccessible - I can't remember
the exact error. I thought it was game up with this drive, but surprisingly
following my reseating the SATA cable and a reboot later it has worked without
further complaints. With reports of OCZ drives failing at an alarming rate
more than a decade ago, I am happy it has lasted this long.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-09 10:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 7:41 [gentoo-user] problem formatting new 256 GB USB stick Philip Webb
2025-02-15 11:50 ` [gentoo-user] " Nuno Silva
2025-02-15 13:31 ` Michael
2025-02-16 2:37 ` Philip Webb
2025-02-16 9:08 ` Nuno Silva
2025-02-16 13:41 ` Michael
2025-02-16 14:48 ` Wols Lists
2025-02-17 23:12 ` Frank Steinmetzger
2025-02-18 11:53 ` Michael
2025-02-19 12:10 ` Frank Steinmetzger
2025-02-20 9:58 ` Michael
2025-02-16 22:57 ` [gentoo-user] problem formatting new 256 GB USB stick : more info Philip Webb
2025-02-17 0:17 ` [gentoo-user] " Nuno Silva
2025-02-17 0:39 ` [gentoo-user] " Michael
2025-02-17 3:43 ` Philip Webb
2025-02-17 9:18 ` Philip Webb
2025-02-17 12:02 ` Michael
2025-02-17 16:33 ` Stroller
2025-02-17 16:19 ` Wols Lists
2025-02-17 17:16 ` [gentoo-user] " Grant Edwards
2025-02-17 18:12 ` Michael
2025-02-18 3:46 ` [gentoo-user] Re: problem formatting new 256 GB USB stick : f3 Philip Webb
2025-02-18 4:43 ` Grant Edwards
2025-02-18 5:53 ` Philip Webb
2025-02-18 9:13 ` Frank Steinmetzger
2025-02-18 19:10 ` [gentoo-user] Re: problem formatting new 256 GB USB stick : alternatives Philip Webb
2025-02-18 21:18 ` Grant Edwards
2025-02-18 23:25 ` Michael
2025-02-19 12:16 ` Frank Steinmetzger
2025-02-19 12:20 ` Frank Steinmetzger
2025-02-20 10:47 ` Michael
2025-02-18 14:40 ` [gentoo-user] Re: problem formatting new 256 GB USB stick : f3 Grant Edwards
2025-02-18 17:00 ` Grant Edwards
2025-02-18 11:57 ` Michael
2025-02-18 18:54 ` [gentoo-user] Re: problem formatting new 256 GB USB stick : glances at gparted Philip Webb
2025-02-18 23:13 ` Michael
2025-02-19 0:47 ` Grant Edwards
2025-02-19 1:12 ` [gentoo-user] alternatives to USB sticks for reliable archiving Philip Webb
2025-02-19 2:28 ` [gentoo-user] " Grant Edwards
2025-02-19 9:48 ` [gentoo-user] " Michael
2025-02-19 3:00 ` [gentoo-user] Re: problem formatting new 256 GB USB stick : glances at gparted eric
2025-02-20 18:18 ` Dale
2025-02-20 22:40 ` Frank Steinmetzger
2025-02-20 23:43 ` Grant Edwards
2025-02-21 8:10 ` Dale
2025-03-08 22:09 ` Frank Steinmetzger
2025-03-08 22:48 ` Dale
2025-03-09 10:31 ` Michael [this message]
2025-03-10 3:32 ` Dale
2025-03-10 13:01 ` Frank Steinmetzger
2025-02-17 16:38 ` [gentoo-user] problem formatting new 256 GB USB stick Stroller
2025-02-17 23:06 ` Frank Steinmetzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6031675.MhkbZ0Pkbq@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox