From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Date: Thu, 3 Sep 2009 21:20:57 -0400 [thread overview]
Message-ID: <0a2891b0ca461335221f7788685fca19@quanstro.net> (raw)
In-Reply-To: <1252025598.16936.5364.camel@work.SFBay.Sun.COM>
On Thu Sep 3 20:53:13 EDT 2009, rvs@sun.com wrote:
> "None of those technologies [NFS, iSCSI, FC] scales as cheaply,
> reliably, goes as big, nor can be managed as easily as stand-alone pods
> with their own IP address waiting for requests on HTTPS."
> http://blog.backblaze.com/2009/09/01/petabytes-on-a-budget-how-to-build-cheap-cloud-storage/
>
> Apart from the obvious comment that I swear I used a quote like that
> to justify 9P more than once, I'm very curious to know how Plan9
> would perform on such a box.
>
> Erik, do you have any comments?
i'm speaking for myself, and not for anybody else here.
i do work for coraid, and i do do what i believe. so
cavet emptor.
i think coraid's cost/petabyte is pretty competitive.
they sell 48TB 3u unit for about 20% more. though
one could not build 1 of these machines since the
case is not commercially available.
i see some warning signs about this setup. it stands
out to me that they use desktop-class drives and the
drives appear hard to swap out. the bandwith out
of the box is 125MB/s max.
aside from that, here's what i see as what you get for
that extra 20%:
- fully-supported firmware,
- full-bandwith to the disk (no port multpliers)
- double the network bandwidth
- ecc memory,
- a hot swap case with ses-2 lights so the tech doesn't
grab the wrong drive,
oh, and the coraid unit works with plan 9. :-)
- erik
next prev parent reply other threads:[~2009-09-04 1:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 0:53 Roman V Shaposhnik
2009-09-04 1:20 ` erik quanstrom [this message]
2009-09-04 9:37 ` matt
2009-09-04 14:30 ` erik quanstrom
2009-09-04 16:54 ` Roman Shaposhnik
2009-09-04 12:24 ` Eris Discordia
2009-09-04 12:41 ` erik quanstrom
2009-09-04 13:56 ` Eris Discordia
2009-09-04 14:10 ` erik quanstrom
2009-09-04 18:34 ` Eris Discordia
[not found] ` <48F03982350BA904DFFA266E@192.168.1.2>
2009-09-07 20:02 ` Uriel
2009-09-08 13:32 ` Eris Discordia
2009-09-04 16:52 ` Roman Shaposhnik
2009-09-04 17:27 ` erik quanstrom
2009-09-04 17:37 ` Jack Norton
2009-09-04 18:33 ` erik quanstrom
2009-09-08 16:53 ` Jack Norton
2009-09-08 17:16 ` erik quanstrom
2009-09-08 18:17 ` Jack Norton
2009-09-08 18:54 ` erik quanstrom
2009-09-14 15:50 ` Jack Norton
2009-09-14 17:05 ` Russ Cox
2009-09-14 17:48 ` Jack Norton
2009-09-04 23:25 ` James Tomaschke
2009-09-14 16:43 erik quanstrom
2009-09-20 20:13 ` Bakul Shah
2009-09-21 3:37 ` erik quanstrom
2009-09-21 17:43 ` Bakul Shah
2009-09-21 18:02 ` erik quanstrom
2009-09-21 18:49 ` Wes Kussmaul
2009-09-21 19:21 ` erik quanstrom
2009-09-21 20:57 ` Wes Kussmaul
2009-09-21 22:42 ` erik quanstrom
2009-09-22 10:59 ` matt
2009-09-21 19:10 ` Bakul Shah
2009-09-21 20:30 ` erik quanstrom
2009-09-21 20:57 ` Jack Norton
2009-09-21 23:38 ` erik quanstrom
2009-09-21 22:07 ` Bakul Shah
2009-09-21 23:35 ` Eris Discordia
2009-09-22 0:45 ` erik quanstrom
[not found] ` <6DC61E4A6EC613C81AC1688E@192.168.1.2>
2009-09-21 23:50 ` Eris Discordia
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=0a2891b0ca461335221f7788685fca19@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).