9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: noam@pixelhero.dev
To: 9fans@9fans.net
Subject: Re: [9fans] Re: neoventi: call for initial testing
Date: Wed, 10 Dec 2025 22:09:09 -0500	[thread overview]
Message-ID: <3783C14B70A3DA028103EB6A2082385A@pixelhero.dev> (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.

What whole thing?  That might be before i was on the list.

_This_ whole thing, neoventi, started because I was fixing bugs in
venti and decided the code wasn't worth saving, it's too badly
designed and implemented.

I'd need more context to know how serious of a problem that is.  It's
entirely plausible that someone got multiple bad SSDs, that doesn't
actually prove venti caused the failure.  I'd be very curious just how
much data was stored on them to cause that.

I've had multiple SSDs fail running other file systems, within a year
or two, including ext4.  Some SSDs just aren't good, in the same way
that I've had hard drives fail within two weeks.  That doesn't mean
all hard drives are bad, let alone that ext4 ruins hard drives!  What
it really means is that QC isn't perfect and/or they're hoping people
just buy another one and don't refund it.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d8ba4236feb5d92-M6d9e685eeb63eec56d1ef59f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2025-12-10 22:56 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
2025-12-10 22:37           ` wb.kloke
2025-12-11  3:09           ` noam [this message]
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=3783C14B70A3DA028103EB6A2082385A@pixelhero.dev \
    --to=noam@pixelhero.dev \
    --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).