From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is fossil/venti file system a good choice for SSD?
Date: Sat, 3 Feb 2018 12:10:55 -0800 [thread overview]
Message-ID: <20180203201110.75A91156E80B@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 03 Feb 2018 18:49:50 +0000." <CACo5X5j1v9cAoxqxEG=1OyfiRdUYFjpfN5dh9F+NK0=WGPAKSw@mail.gmail.com>
On Sat, 03 Feb 2018 18:49:50 +0000 "Digby R.S. Tarvin" <digbyt42@gmail.com> wrote:
Digby R.S. Tarvin writes:
>
> My experience of running normal (read mostly) Linux filesystems on solid
> state media is that SSD is more robust but far less reliable than rotating
> media.
>
> MTBF for rotating media for me has been around 10 years. MTBF for SSD has
> been about 2. And the SSD always seems to fail catastrophically - appearing
> to work fine one day, then after an inexplicable crash, half the media is
> unreadable. I assume this is something to do with the wear leveling, which
> successfully gets most of the blocks to wear out at the same time with no
> warning. If I reformat and reload the SSD to correct all the mysterious
> corruptions, it last a few weeks, then does the same thing again.
MTTF doesn't make much sense for SSDs. A 1TB SSD I bought a
couple years ago has a rating of 300 TB written, an MTBF of 2M
hours and a 10 year warranty. It can do over 500MB/s of
sequential writes. If I average 9.5MB/s writes, it will last
year. If I continuoulsy write 100MB/s, it will last under 35
days. In contrast the life of an HDD depends on how long it
has been spinning, seeks, temperature and load/unloads. A disk
with 5 year warraty will likely last 5 years even if you write
100MB/s continuously.
And consumer HDSC cards such as the ones used in cameras and
Raspi are much much worse.
In practice an SSD will last much longer than a HDD since
average write rates are not high for the typical things people
do.
next prev parent reply other threads:[~2018-02-03 20:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 9:39 lchg
2018-02-03 10:54 ` Ethan Grammatikidis
2018-02-03 12:45 ` Steve Simon
2018-02-03 13:25 ` hiro
2018-02-03 14:53 ` Steve Simon
2018-02-03 16:53 ` hiro
2018-02-03 18:49 ` Digby R.S. Tarvin
2018-02-03 20:10 ` Bakul Shah [this message]
2018-02-03 21:46 ` Digby R.S. Tarvin
2018-02-03 23:46 ` Bakul Shah
2018-02-04 9:45 ` [9fans] RasPi why? Ethan Grammatikidis
2018-02-04 15:05 ` Rui Carmo
2018-02-04 16:36 ` Steve Simon
2018-02-04 21:00 ` Lyndon Nerenberg
2018-02-04 21:55 ` Bakul Shah
2018-02-04 22:23 ` hiro
2018-02-04 23:46 ` Skip Tavakkolian
2018-02-04 23:52 ` Lyndon Nerenberg
2018-02-05 9:22 ` hiro
2018-02-05 9:27 ` Rui Carmo
2018-02-05 9:48 ` hiro
2018-02-05 9:49 ` hiro
2018-02-04 10:02 ` [9fans] Is fossil/venti file system a good choice for SSD? hiro
2018-02-04 23:46 ` Bakul Shah
2018-02-05 8:50 ` hiro
2018-02-04 9:52 ` hiro
2018-02-04 16:15 ` Digby R.S. Tarvin
2018-02-04 21:46 ` hiro
2018-02-04 22:47 ` Digby R.S. Tarvin
2018-02-05 9:54 ` hiro
2018-02-04 9:49 ` hiro
2018-02-04 22:22 ` Ole-Hjalmar Kristensen
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=20180203201110.75A91156E80B@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--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).