From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server?
Date: Thu, 13 Aug 2009 18:23:50 -0700 [thread overview]
Message-ID: <7d3530220908131823u1d5e3b9bk22632a1cce07f38b@mail.gmail.com> (raw)
In-Reply-To: <47a50044bb220c4db0592a2aacb694f6@quanstro.net>
On Thu, Aug 13, 2009 at 6:01 PM, erik quanstrom<quanstro@quanstro.net> wrote:
>> So, I guess that means venti+fossil+cpu on one headless machine in
>> some forgotten corner of the datacentre.
>
> regardless of one's terminal accomidations, i still think it makes
> a lot of sense to have a stand-alone fileserver. it really does stink
> if your fs goes down for no reason at all. this is especially true if
> you're doing a lot of experimenting or don't have a proper terminal.
>
> in fact, i think it makes sense to devote two machines to one's
> fileserver. one diskless fileserver and an coraid storage appliance. :-)
>
> shameless, aren't i?
>
> - erik
>
>
This is what we do at Sandia. We have one machine which serves
cpu/auth/file, but the actual Venti disks are in a Coraid connected
via GigE. The fossil disk is in the server, but if it dies we can just
build a new one.
John
--
"Object-oriented design is the roman numerals of computing" -- Rob Pike
next prev parent reply other threads:[~2009-08-14 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 0:30 Benjamin Huntsman
2009-08-14 0:55 ` andrey mirtchovski
2009-08-14 1:01 ` erik quanstrom
2009-08-14 1:23 ` John Floren [this message]
2009-08-14 2:00 ` erik quanstrom
2009-08-14 6:14 ` Lyndon Nerenberg
2009-08-14 8:45 ` Robert Raschke
2009-08-14 12:07 ` erik quanstrom
2009-08-14 12:44 ` Robert Raschke
2009-08-14 12:09 ` erik quanstrom
2009-08-16 2:12 ` Adrian Tritschler
2009-08-14 4:16 ` Lyndon Nerenberg
2009-08-14 1:09 ` Federico G. Benavento
2009-08-14 1:15 ` blstuart
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=7d3530220908131823u1d5e3b9bk22632a1cce07f38b@mail.gmail.com \
--to=slawmaster@gmail.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).