From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] file server speed
Date: Wed, 16 Jul 2014 20:23:08 +0530 [thread overview]
Message-ID: <CAA6Yd9U4u42UtN1bLvyBeoTZ104_PwRUY2jmo3EffOaPLPN_FA@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKH1gyK3HyTSM7Qz_HbhN34C7dmYiUHfnGuS7p-74poOTA@mail.gmail.com>
On Wed, Jul 16, 2014 at 7:53 PM, Steven Stallion <sstallion@gmail.com> wrote:
> On Tue, Jul 15, 2014 at 7:04 PM, <kokamoto@hera.eonet.ne.jp> wrote:
>>> not a fair comparsion.
>>
>> Yes, I'd have been more specific.
>> my intension was cwfs > fossil+venti of 9atom >> fossil+venti labs.
>> I did not consider kenfs itself, because I consider it should be
>> file+auth+cpu server. The last is not important, but for drawterm
>> from others.
>>
>> Recent kenfs can be such a machine?
>> Please remember I plan it for my private home machine, not
>> any sofisticated office use.
>
> kenfs works well, but you have to be well prepared to maintain it.
> Invest in a decent UPS - preferably one that is supported by the
> auto-shutdown (ISTR support was added for that a while back). You need
> to be careful when sizing your cache - I would invest in a pair of
> decent SSDs for cache, and two or more drives for housing the WORM. Be
> prepared for failure. The last large kensfs I maintained (around 16TB
> usable, 48TB raw) worked very well but would still crash one every
> year or two. Make sure you keep hard copies of your fsconfig and get
> comfortable with scripting as erik mentioned.
>
> That was in an office environment. At home I use
> fossil+(plan9port)venti running on linux-based NAS. This ends up
> working very well for me since I have resources to spare on that
> machine. This also lets me backup my arenas via CrashPlan. I use a
I am very interested to use such a setup. Could you please add more
about the setup? What hardware do you use for the NAS? Any scripts
etc?
--
Ramakrishnan
next prev parent reply other threads:[~2014-07-16 14:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 6:13 kokamoto
2014-07-15 13:02 ` Anthony Sorace
2014-07-15 16:30 ` cinap_lenrek
2014-07-15 16:56 ` erik quanstrom
2014-07-16 0:04 ` kokamoto
2014-07-16 0:36 ` kokamoto
2014-07-16 17:26 ` erik quanstrom
2014-07-16 14:23 ` Steven Stallion
2014-07-16 14:53 ` Ramakrishnan Muthukrishnan [this message]
2014-07-17 1:13 ` Steven Stallion
2014-07-17 17:13 ` Ramakrishnan Muthukrishnan
2014-07-17 21:44 ` cam
2014-07-16 17:41 ` erik quanstrom
2014-07-16 23:15 ` kokamoto
2014-07-17 0:29 ` Steven Stallion
2014-07-17 0:31 ` Steven Stallion
2014-07-17 1:10 ` john francis lee
2014-07-17 1:09 ` john francis lee
2014-07-17 1:10 ` Bakul Shah
2014-07-17 16:56 ` erik quanstrom
2014-07-17 18:14 ` Bakul Shah
2014-07-17 18:39 ` erik quanstrom
2014-07-17 19:01 ` Bakul Shah
2014-07-17 19:10 ` erik quanstrom
2014-07-17 19:26 ` Bakul Shah
2014-07-16 17:23 ` erik quanstrom
2014-07-16 23:01 ` kokamoto
2014-07-17 17:03 ` erik quanstrom
2014-07-18 16:50 ` hiro
2014-07-18 19:36 ` erik quanstrom
2014-07-18 20:11 ` Bakul Shah
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=CAA6Yd9U4u42UtN1bLvyBeoTZ104_PwRUY2jmo3EffOaPLPN_FA@mail.gmail.com \
--to=vu3rdd@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).