9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] anyone put their venti on an SSD?
Date: Fri,  3 May 2013 18:47:45 -0700	[thread overview]
Message-ID: <D81CC0A5-167F-44C2-AB8D-7DB8FCB1C5AD@orthanc.ca> (raw)
In-Reply-To: <50aeef7ec4d88fc34df93346b304d58c@rei2.9hal>


On 2013-05-03, at 6:31 PM, cinap_lenrek@gmx.de wrote:

> ocz seems to have a bad reputation. just googled "intel ssd broken"
> and you get tons of results from people with broken/dead ocz ssd's.

Disk drive reliability comes and goes with the seasons.  For years I only ran Seagate disks, and wouldn't go near WD.  Then, after a 30% failure run on < 1 year old Seagates, I switched back to WDs, which have been flawless for me.  So far.  And Hitachi has drifted in and out of the picture over the years.

Ask anyone else and they will tell you a partially to completely different story.  At $80 for a couple of TB, I'll just toss them out when they break.  And while SSD isn't anywhere near that inexpensive yet, it's finally down into the price range where you can call it commodity disk.  These days I'm paying a bit under $1/GB for SSD.  That's cheap enough that I can afford to experiment with smaller sized drives in non-critical applications.

I have a FreeBSD box that's been running off an OCZ Vertex 3 for a few months now without issue. It does regular buildworlds and the like, so I'm not gentle on the write volume.  UFS TRIM support seems to work fine, and if you chose to believe the smart stats, the (128 GB) disk is error free after having many TB written to it.  Many claim Sandforce disks will blow up well before this.  I'm beginning to think otherwise, although my sample space is not statistically significant.

I have a pair of Vertex 4s I haven't installed yet.  I'm curious to see how much (or if) the new OCZ controllers work.  The benchmarks I've read are impressive.  I'm planning to put one into my Mac Mini.  If MacOS and its several hundred GB VM footprint can't kill an SSD, nothing will ;-)

--lyndon




  parent reply	other threads:[~2013-05-04  1:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 14:19 Steve Simon
2013-05-03 14:28 ` a
2013-05-03 20:59 ` geoff
2013-05-03 21:51   ` Matthew Veety
2013-05-03 21:58   ` cinap_lenrek
2013-05-04  1:59     ` erik quanstrom
2013-05-04  4:17       ` cinap_lenrek
2013-05-04  6:17         ` erik quanstrom
2013-05-03 23:59   ` Charles Forsyth
2013-05-04  1:31     ` cinap_lenrek
2013-05-04  1:41       ` Devon H. O'Dell
2013-05-04  1:47       ` Lyndon Nerenberg [this message]
2013-05-04  1:51         ` erik quanstrom
2013-05-04  1:57           ` Lyndon Nerenberg
2013-05-04  2:00             ` erik quanstrom
2013-05-04  2:03               ` Lyndon Nerenberg
2013-05-04  2:13               ` Kurt H Maier
2013-05-04  2:17                 ` erik quanstrom
2013-05-04  5:50     ` Charles Forsyth
2013-05-04  6:22       ` Bakul Shah
2013-05-04  1:16   ` Lyndon Nerenberg
2013-05-04  1:43     ` erik quanstrom
2013-05-04  1:50       ` Lyndon Nerenberg
2013-05-04  3:41       ` Steven Stallion
2013-05-04  4:19         ` cinap_lenrek
2013-05-04  4:46           ` Lyndon Nerenberg
2013-05-04  3:26 ` Steven Stallion
2013-05-04  6:44   ` erik quanstrom
2013-05-04 18:09     ` Steven Stallion

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=D81CC0A5-167F-44C2-AB8D-7DB8FCB1C5AD@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).