From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] file server speed
Date: Thu, 17 Jul 2014 12:56:30 -0400 [thread overview]
Message-ID: <1cd7faec083da0c4468343b048db7ddc@ladd.quanstro.net> (raw)
In-Reply-To: <CAGGHmKHV+Ahnx7WkQvSQ0b_arEQ0bZoCWXM96D-f6e1scvqBHQ@mail.gmail.com>
> I've used ReadyNAS appliances at home for almost 10 years. The current
> product line is made up of low-power Atoms. I'm running a RAID5 across
> 4 500G enterprise SATA drives (that should indicate how old this unit
> is pretty well...) I have a wired network primarily in the rack in the
> office at home - I absolutely would not use wireless to connect fossil
> to venti (fossil does *not* cope well with the connection to venti
> dropping).
so this is absolutely a potential problem with ken's file server using
aoe storage.
the way i delt with the problem is to wait forever for aoe to come back.
since there's no connection, there is no procedure for reestablishing a
connection. there is also no overhead like a proxy connection.
i gave a little paper at iwp9 about the "diskless file server" and a few
weeks after we got back a bug in the storage caused it to stop responding.
we were able to fix the storage, load a new image, and restart the storage
kernel. the file server didn't miss a beat and none of the cpu servers had
any issues.
i would think the same approach would work with fossil. of course one
would need a more sophisticated solution than "just wait forever", due to
the tcp connection.
- erik
next prev parent reply other threads:[~2014-07-17 16:56 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
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 [this message]
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=1cd7faec083da0c4468343b048db7ddc@ladd.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).