9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Throwing in the Towel
Date: Sun, 26 May 2024 21:06:14 -0400	[thread overview]
Message-ID: <16277.1716771974@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <17167523800.5BBf3dBb0.7751@composer.9fans.topicbox.com>

> Can it be the case that the venti index file exhibits a desastrous
> write pattern for SSDs?

Maybe... but it would need to be worse than the load provided by
other file systems, including FAT and ext2/3/4.  Some of those
file systems rewrite some blocks like mad (e.g., superblock, journal
blocks).

Just because a flash translation layer might need to erase an entire
megabyte, or multiple megabytes, does not mean that it needs to put
the new value of a logical block in the same area of the flash that
the old value of that logical block used to be in (they do the opposite).

It would be interesting to get a dump of the SMART data for the drive(s)
that went bad, and also drive(s) that didn't go bad.

Dave Eckhardt

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2ca67486c7a13a77-Mda9b0251a0482ce40f14c606
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-05-27  1:06 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 [this message]
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
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=16277.1716771974@lunacy.ugrad.cs.cmu.edu \
    --to=davide+p9@cs.cmu.edu \
    --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).