From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Survey: Current Fossil+venti Filesystem
Date: Thu, 23 Jun 2011 12:37:49 -0400 [thread overview]
Message-ID: <9e287164146271782e2b4d83398bb993@ladd.quanstro.net> (raw)
In-Reply-To: <BANLkTimZTQ8sLsQXqyO3L_0+_VnbVhfDLA@mail.gmail.com>
> The main point I took from the talk they gave was that failure was
> most strongly related to the number of writes in FLASH. If your
> striping strategy is to duplicate writes to each drive, you faced the
> happy prospect of doing a write and having both drives fail at the
> same time. Hard drives have a different way of failing. We've seen
> weirdness like this here, with drives in a bunch of nodes that all
> seem to fail simultaneously, well within rated lifetime. Not cheap
> drives either. Of course that was a little while ago and things seem
> to have gotten better, but it's worth a warning.
that's very interesting. i haven't seen that at all. the drives
that i've seen fail in bunches have been regular old hard drives.
- erik
next prev parent reply other threads:[~2011-06-23 16:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 13:50 Jack Norton
2011-06-22 14:02 ` erik quanstrom
2011-06-22 15:13 ` Charles Forsyth
2011-07-03 9:07 ` Steve Simon
2011-06-23 8:46 ` David du Colombier
2011-06-23 10:03 ` Richard Miller
2011-06-23 10:35 ` Adrian Tritschler
2011-06-23 14:51 ` Jack Norton
2011-06-23 15:25 ` dexen deVries
2011-06-23 15:27 ` erik quanstrom
2011-06-23 15:57 ` ron minnich
2011-06-23 16:19 ` erik quanstrom
2011-06-23 16:28 ` ron minnich
2011-06-23 16:37 ` erik quanstrom [this message]
2011-06-23 18:47 ` Bakul Shah
2011-06-24 22:44 ` Akshat Kumar
2011-06-23 16:56 ` Charles Forsyth
2011-06-23 16:58 ` Charles Forsyth
2011-06-23 17:02 ` Jack Norton
2011-06-23 17:50 ` erik quanstrom
2011-06-23 15:27 ` Charles Forsyth
2011-06-23 15:57 ` David du Colombier
2011-06-23 16:20 ` smiley
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=9e287164146271782e2b4d83398bb993@ladd.quanstro.net \
--to=quanstro@quanstro.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).