9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti ports and productization
Date: Tue, 21 Oct 2003 11:50:31 -0400	[thread overview]
Message-ID: <E1ABymF-0000VR-7q@t40.swtch.com> (raw)
In-Reply-To: Your message of "Tue, 21 Oct 2003 11:35:24 EDT." <a94945571995ec9c748ca80622e3d404@9srv.net>

> that's very interesting. my comment about "why rewrite" wasn't
> intended to necessarily imply it should've been done that way,
> although i realize it probably came off that way. what about
> the current implementation is at issue? and (the big question)
> is it expected that the new stuff will be protocol compatable?

The protocol is almost completely trivial.  There are only two
interesting messages -- read and write.  So ultimately it really
doesn't matter.

We have had problems with Venti since the Seans left,
but I am not convinced that we really need to start over
(perhaps I am the only one!).  We have had some problems
with the big Venti server, but my understanding is that
all of the problems appeared to be disk corruption rather
than software error.  I think the biggest problem is that
before the Seans left they didn't get the system scanning
itself for damage regularly.  Disks are going to fail and
we need to replace them, but we haven't been.  This does
contrast with the WORM, where the platters fail much less
frequently.

Then again, the amount of code involved is so small that
I do think that bulk alone doesn't justify sticking with
the current code if you want to start over.

If I started over, I suspect I would end up writing
substantially the same code, so I don't see the point.

Russ


  reply	other threads:[~2003-10-21 15:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-11  0:37 a
2003-10-11  1:45 ` jmk
2003-10-11  1:50 ` bs
2003-10-11  2:14 ` Russ Cox
2003-10-11 17:05   ` a
2003-10-21 10:14 ` Martin C.Atkins
2003-10-21 10:20   ` a
2003-10-21 14:26     ` jmk
2003-10-21 15:35       ` a
2003-10-21 15:50         ` Russ Cox [this message]
2003-10-21 18:24           ` rog
2003-10-22  4:33           ` okamoto
2003-10-22  5:15             ` okamoto
2003-10-22  9:48               ` a
2003-10-22 14:57           ` Richard Miller
2003-10-22 16:54             ` jmk
2003-10-21 17:20         ` Scott Schwartz
2003-10-21 21:30           ` C H Forsyth
2003-10-21 22:13             ` Dan Cross
2003-10-21 16:05   ` Rob Pike
2003-10-21 16:50     ` rog
2003-10-22  9:52     ` Martin C.Atkins

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=E1ABymF-0000VR-7q@t40.swtch.com \
    --to=rsc@swtch.com \
    --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).