9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: California Electric <californiaelectric@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] What does your fileserver consist of?
Date: Wed, 12 Oct 2016 08:31:48 -0700	[thread overview]
Message-ID: <F9B430BF-17C3-4FF4-A22A-E5AC27FDD2F5@gmail.com> (raw)
In-Reply-To: <CAPd04b4MPq10Z9CZOFfyT9ja_hRd_yc4mkOJ75puYgyeDNJW8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

Jim,

There are other low cost alternatives than an rpi. Higher kilowatt-hour cost for sure than an rpi, but cheap...

My current 32bit bell labs distro file server is a Lenovo (IBM) m58p small form factor. It has a 3.33 ghz intel core2 duo cpu, upgraded from it's stock 3.0ghz core2 duo. I have also tested it with a 3.0ghz core2 quad cpu, and that works. With AHCI set to native everything works, including multiple cores and built in gigabit ethernet. I boot off a USB stick, and it runs a 512GB fossil from SSD. I bought mine for 60 $US on eBay. I just checked and they are as low as half that now. Tilted on its side it doesn't take up much shelf space at all.

The fossil is backed by a very large venti running under plan9port on a mac that does other things, too. 

My auth server is an rpi though, the original, and it sits on top and gets its power from one of the USB ports on the fs, so it's all pretty compact and a single switch.

Greg



Sent from my iPhone
> On Oct 11, 2016, at 5:33 PM, James A. Robinson <jim.robinson@gmail.com> wrote:
> 
> Folks,
> 
> One of the things I'm thinking about is setting up a full Plan 9
> cluster, meaning one of the components would be a stand-alone
> fileserver hooked up to a decent amount of storage.
> 
> I was wondering what experience people have had with slower or faster
> machines in this role?
> 
> I was wondering whether or not it'd be feasible to hook up something
> like http://tinyurl.com/jgov5gc (Amazon.com) to something small like a
> Raspberry Pi 3, or if the I/O would be too much for that kind of
> computer to handle.
> 
> Does anyone here run a fileserver on a small computer like a
> raspberry pi 3, or perhaps something like an Intel nuc?
> 
> I wouldn't be supporting multiple users, just myself moving between
> a couple of devices.
> 
> Jim


[-- Attachment #2: Type: text/html, Size: 2846 bytes --]

  parent reply	other threads:[~2016-10-12 15:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  0:33 James A. Robinson
2016-10-12  5:27 ` Tyga
2016-10-12  9:20   ` Sergey Zhilkin
2016-10-12  9:22     ` Sergey Zhilkin
2016-10-12  9:48 ` Richard Miller
2016-10-12 14:46 ` Steven Stallion
2016-10-12 15:31 ` California Electric [this message]
2016-10-12 18:13   ` Steve Simon
2016-10-12 18:26 ` Brantley Coile
2016-10-12 22:38   ` James A. Robinson
2016-10-12 22:39     ` Brantley Coile
2016-10-12 23:19       ` Jules Merit
2016-10-13 15:54       ` James A. Robinson
2016-10-22 18:21         ` James A. Robinson
2016-10-22 21:06           ` Steven Stallion
2016-10-22 21:40             ` Steve Simon
2016-11-06 21:58               ` Tharaneedharan Vilwanathan
2016-11-10  5:21                 ` James A. Robinson
2016-11-10  5:41                   ` Tharaneedharan Vilwanathan

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=F9B430BF-17C3-4FF4-A22A-E5AC27FDD2F5@gmail.com \
    --to=californiaelectric@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).