From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Throwing in the Towel
Date: Wed, 29 May 2024 07:40:19 +0100 [thread overview]
Message-ID: <5B3282E2-DB89-4C78-8901-B2832E1EBB64@quintile.net> (raw)
In-Reply-To: <6CF300A17E86168075C422519C7A1A24@eigenstate.org>
i can only speak from experience, but i have had fossil and venti running on a single ssd (on a radpberry pi) for 5 years now - no rotating discs left at home.
i have mtime changes and ephemeral snapshots turned off to reduce the update rate. i chose a sandisk card, and take backups just in case…
so far so good.
-Steve
> On 29 May 2024, at 4:39 am, ori@eigenstate.org wrote:
>
> Finally,. SSDs just die over time. Especially if they are
> not powered on and refreshing. JEDEC specs say that they
> should retain data for 1 year unplugged when stored at 30
> degrees celsius, assuming the internet isn't lying to me.
>
> Keep backups.
>
> Quoth Dave Eckhardt <davide+p9@cs.cmu.edu>:
>>> For the napkin calculation: On disk, the IEntry is 38Bytes. Alas,
>>> writes occur always in (the ssd internal) blocksize. So, essentially
>>> (assuming 4096 byte blocksize, which is quite optimistic), we have
>>> a write efficiency of less than 1 percent.
>>
>> While I see how such a model can predict disaster, I don't think that
>> model matches how FTLs work, because it can't.
>>
>> Many file systems (FAT, ext2/3/4) write the same logical block over
>> and over and over and over and over. I think the default interval
>> for ext4 to synch the superblock and the journal is five seconds,
>> which if true is more than 15,000 times every *day* for a busy
>> file system (and I think lots of Linux systems are busy in that
>> sense).
>>
>>> A good firmware in the ssd could avoid needing a new block for the
>>> write, if all bits are changed in teh same direction by the new
>>> data.
>>
>> Again, I believe this model predicts that no regular Linux file
>> system can be used on any SSD, thus I believe this model is not
>> accurate.
>>
>> To quote Wikipedia:
>>
>> https://en.wikipedia.org/wiki/Flash_memory_controller
>>
>>> The mapping units of an FTL can differ so that LBAs are mapped
>>> block-, page- or even sub-page-based. Depending on the usage
>>> pattern, a finer mapping granularity can significantly reduce
>>> the flash wear out and maximize the endurance of a flash based
>>> storage media.
>>
>> Also, I feel as if this point is several assumption layers deep.
>> I think one user reported an unknown number of failures in two
>> sets of SSDs of unknown brand and model. I don't think we know
>> that it was venti SSDs that went bad as opposed to fossil SSDs,
>> let alone knowing it was index SSDs for venti.
>>
>>> It seems, venti in its current form is a ssd killer, if they
>>> are used for the isects.
>>
>> I don't think this claim is yet supported well.
>>
>> Dave Eckhardt
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2ca67486c7a13a77-M8bfe23b05de7c8450157011c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2024-05-29 6:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 15:13 Steven Stallion
2024-05-04 19:16 ` [9fans] Plan9 wept! - " Alexandr Babic
2024-05-04 20:21 ` [9fans] " Shawn Rutledge
2024-05-04 20:37 ` wb.kloke
2024-05-26 19:39 ` wb.kloke
2024-05-26 21:20 ` Riddler
2024-05-27 1:06 ` Dave Eckhardt
2024-05-28 19:33 ` wb.kloke
2024-05-28 21:49 ` Charles Forsyth
2024-05-29 2:22 ` Dave Eckhardt
2024-05-29 3:32 ` ori
2024-05-29 6:40 ` Steve Simon [this message]
2024-05-29 8:29 ` wb.kloke
2024-05-29 8:17 ` hiro
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=5B3282E2-DB89-4C78-8901-B2832E1EBB64@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).