From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] FS replication et al.
Date: Tue, 11 Dec 2001 14:04:09 +0200 [thread overview]
Message-ID: <20011211140409.H2954@cackle.proxima.alt.za> (raw)
I've been wondering: could the dump filesystem (I confess I still have
only a very vague understanding of the mechanics involved) merge two
or more update streams and retain their identities?
And could one configure two dump servers to accept each other's
modified blocks (assuming they both start from the same original
filesystem) to provide a form of replication?
I suppose what I'm asking is how much effort would be involved in
adding such features - were they found to be useful - either to
the existing fileserver or to the one presently under development.
++L
reply other threads:[~2001-12-11 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011211140409.H2954@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).