From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Date: Tue, 8 Sep 2009 13:16:24 -0400 [thread overview]
Message-ID: <728aafe49c38f76663622f541315ed73@quanstro.net> (raw)
In-Reply-To: <4AA68C13.7080400@0x6a.com>
> I read the paper you wrote and I have some (probably naive) questions:
> The section #6 labeled "core improvements" seems to suggest that the
> fileserver is basically using the CPU/fileserver hybrid kernel (both
> major changes are quoted as coming from the CPU kernel). Is this just a
> one-off adjustment made by yourself, or have these changes been made
> permanent?
it's not a hybrid kernel. it is just a file server kernel. of course
the same c library and whatnot are used. so there are shared
bits, but not many.
it is a one-off thing. i also run the same fileserver at home.
the source is on sources as contrib quanstro/fs. i don't think
anybody else runs it.
> Also, about the coraid AoE unit: am I correct in assuming that it does
> some sort of RAID functionality, and then presents the resulting
> device(s) as an AoE device (and nothing more)?
exactly.
> Also, another probably dumb question: did the the fileserver machine use
> the AoE device as a kenfs volume or a fossil(+venti)?
s/did/does/. the fileserver is running today.
the fileserver provides the network with regular 9p fileserver
with three attach points (main, dump, other) accessable via il/ip.
from a client's view of the 9p messages, fossil, fossil+venti and
ken's fs would be difficult to distinguish.
- erik
next prev parent reply other threads:[~2009-09-08 17:16 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
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 [this message]
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=728aafe49c38f76663622f541315ed73@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).