From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] Re: neoventi: call for initial testing
Date: Wed, 10 Dec 2025 17:36:41 -0500 [thread overview]
Message-ID: <FFA706F40591152A944A552E456DF2BD@eigenstate.org> (raw)
In-Reply-To: <17654041140.0d3203CD.19331@composer.9fans.topicbox.com>
Quoth wb.kloke@gmail.com:
>
>
> It siems that you did not remember, that the whole thing startet by the report of one member on this list, that his installation, which provided plan9 software failed after using up more than 1 ssd.
>
Hardware dies sometimes. Especially SSDs, if they have spent a good portion of their lives powered off.
For example, some models used in production at Backblaze had failure rates approaching 10%/year:
https://backblazeprod.wpenginepowered.com/wp-content/uploads/2023/09/7-Select-SSD-Lifetime-AFR-Table-1.png
What has been done to show that SSDs used under venti die at a higher rate than they would otherwise?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d8ba4236feb5d92-M9da3859af50b07371f67729d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2025-12-10 22:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 22:30 [9fans] neoventi: call for initial testing noam
2025-12-10 18:54 ` [9fans] " wb.kloke
2025-12-10 20:59 ` ori
2025-12-10 21:20 ` wb.kloke
2025-12-10 21:36 ` ori
2025-12-10 21:56 ` wb.kloke
2025-12-11 3:06 ` noam
2025-12-11 3:13 ` noam
2025-12-11 1:59 ` noam
2025-12-11 1:58 ` noam
2025-12-10 21:53 ` ori
2025-12-11 3:11 ` noam
2025-12-11 3:21 ` noam
2025-12-10 22:01 ` wb.kloke
2025-12-10 22:36 ` ori [this message]
2025-12-10 22:37 ` wb.kloke
2025-12-11 3:09 ` noam
2025-12-11 0:01 ` [9fans] Venti: design discussion noam
2025-12-10 20:28 ` wb.kloke
2025-12-10 20:49 ` Steve Simon
2025-12-11 1:16 ` noam
2025-12-10 21:22 ` wb.kloke
2025-12-11 1:52 ` noam
2025-12-10 22:07 ` wb.kloke
2025-12-12 12:08 ` [9fans] neoventi: call for initial testing Charles Forsyth
2025-12-12 17:57 ` wb.kloke
2025-12-13 0:42 ` noam
2025-12-13 0:39 ` noam
2026-01-09 5:50 ` noam
2026-01-09 13:24 ` wb.kloke
2026-01-09 14:31 ` wb.kloke
2026-01-09 16:07 ` Noam Preil
2026-01-09 16:06 ` Noam Preil
2026-01-09 5:54 ` noam
2026-01-09 17:10 ` wb.kloke
2026-01-10 20:23 ` Noam Preil
2026-01-09 17:14 ` Calvin via 9fans
2026-01-09 18:30 ` wb.kloke
2026-01-10 2:08 ` Calvin via 9fans
2026-01-10 10:46 ` Emery
2026-01-21 1:53 ` ori
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=FFA706F40591152A944A552E456DF2BD@eigenstate.org \
--to=ori@eigenstate.org \
--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).