From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] FileServer grid
Date: Tue, 10 Feb 2009 23:05:19 -0800 [thread overview]
Message-ID: <13224789a5f3d055ad4ec9f48e3b7d5e@9netics.com> (raw)
In-Reply-To: <e1d437a40902101341v64e24467t14a88020ba2dda28@mail.gmail.com>
starting with something like /sys/src/cmd/nfs.c or ramfs.c
and a setup like this:
mount /stuff /n/node0
import node1 /stuff /n/node1
import node2 /stuff /n/node2
fscreate and fsopen would create or open /n/node[012]/file and fswrite
would write to /n/node[012]/file. a good developer (not necessarily a
superstar) could write it in a week.
but this assumption -- that this would work better than if all the
nodes accessed a reliable file server -- is wrong.
> is it too much for a syntetic filesystem 9P based? or too few?
>
>
>
> On Tue, Feb 10, 2009 at 5:37 PM, ron minnich <rminnich@gmail.com> wrote:
>
>> On Tue, Feb 10, 2009 at 12:06 AM, Giacomo Tesio <giacomo@tesio.it> wrote:
>>
>> > If a sincronization system for the grid nodes (or a sintetic filesystem
>> > providing access to the grid and replicating writes among node) would
>> > require more than 3 weeks of man work probably I've no chance to get this
>> > solution approved.
>>
>> 3 weeks? I think you have a problem here. Stop now.
>>
>> This is a non trivial problem. At least from what I know.
>>
>> ron
>>
>>
next prev parent reply other threads:[~2009-02-11 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 22:26 Giacomo Tesio
2009-02-06 22:41 ` Roman V. Shaposhnik
2009-02-07 17:32 ` Giacomo Tesio
2009-02-07 22:57 ` Uriel
2009-02-07 23:00 ` erik quanstrom
2009-02-08 1:43 ` Uriel
2009-02-08 15:24 ` Giacomo Tesio
2009-02-08 17:12 ` ron minnich
2009-02-09 8:12 ` Giacomo Tesio
2009-02-10 3:52 ` Roman Shaposhnik
2009-02-10 8:06 ` Giacomo Tesio
2009-02-10 16:37 ` ron minnich
2009-02-10 21:41 ` Giacomo Tesio
2009-02-11 7:05 ` Skip Tavakkolian [this message]
2009-02-10 22:03 ` Roman V. Shaposhnik
2009-02-25 0:09 ` Enrico Weigelt
2009-02-06 22:53 ` erik quanstrom
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=13224789a5f3d055ad4ec9f48e3b7d5e@9netics.com \
--to=9nut@9netics.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).