From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] central list of bugs [replica]
Date: Mon, 27 Oct 2008 09:26:54 -0400 [thread overview]
Message-ID: <08d1e5e8e3020c289ce793a60942b5c9@quanstro.net> (raw)
In-Reply-To: <d3d8045962d57a9d3f005657cc57b358@quintile.net>
about the replica bug
> There is an errata page on the wiki, however
> I doubt there is anyone looking at this and fixing
> the bugs.
>
> The bottom line is if you discover a bug, and it anoys you,
> fix it (you have the source). If you are feeling friendly
> submit a patch.
in order to pull the history from the old 32-bit fileserver at
Coraid to the new 64-bit diskless one, i fixed the problem
with replica mentioned on the errata page. there are also
a few bonus go-fast tricks, including copying only the tail
of append-only files. the old fs was quite slow. the source
code is in /n/sources/contrib/quanstro/src/replica and the
note how how i migrated history is here
http://www.quanstro.net/plan9/history.pdf
in addition to cphist, i modified applylog and friends to
deal with directories changing to files and a few other
wierd corner cases that a 5-year-old fs with many users
grows.
the go-fast tricks (which were necessary — the migration
still took two weeks) are the reason cphist is not in the
distribution.
- erik
next prev parent reply other threads:[~2008-10-27 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 8:39 [9fans] central list of bugs Rudolf Sykora
2008-10-27 11:13 ` hiro
2008-10-27 12:20 ` Steve Simon
2008-10-27 13:26 ` erik quanstrom [this message]
2008-10-30 15:51 ` Enrico Weigelt
2008-10-31 4:42 ` Uriel
2008-10-31 9:24 ` Rudolf Sykora
2008-10-31 11:04 ` Laurent Malvert
2008-10-31 12:53 ` Eric Van Hensbergen
2008-11-01 18:57 ` Enrico Weigelt
2008-11-01 19:35 ` Eric Van Hensbergen
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=08d1e5e8e3020c289ce793a60942b5c9@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).