From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Venti and the hash / public key in plan9
Date: Mon, 6 Feb 2006 10:25:44 -0700 [thread overview]
Message-ID: <43E78698.9020103@lanl.gov> (raw)
In-Reply-To: <45219fb00602060916p5b354e0r@mail.gmail.com>
Lluís Batlle wrote:
> 2006/2/6, Russ Cox <rsc@swtch.com>:
>
>>> Anyway I've don't
>>>understood what does Venti do when a hash is found in the stored
>>>blocks, and the contents of the blocks are different (the
>>>low-probability case). I imagine there is some code which does not
>>>give a data-loss... Can someone give a small explanation about that?
>>
>>It responds to the write RPC with an error.
>
> So what should manage that error? The application? Maybe it try a
> different write size?
> In fact there should be another application layer between 9p and the
> RPC for venti, isn't it? (which?)
Lluis, in a system like this, if two blocks have the same hash, they are
by definition the same. It therefore makes no sense to say 'what if the
data is different'. The data is not, from the viewpoint of venti. So a
write of a block with hash X, when a block of hash X already exists in
venti, is an error. It's the same data. So you get an error on the write
RPC.
So your real question is, 'what if a block B' has the same hash as a
block B? What does venti do?" It returns B, not B', as it should. That's
the underlying rule. That's one reason you want a long hash, with a good
design :-)
Now, let's see if I got this right :-)
ron
prev parent reply other threads:[~2006-02-06 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:36 Lluís Batlle
2006-02-06 16:58 ` Russ Cox
2006-02-06 17:16 ` Lluís Batlle
2006-02-06 17:21 ` "Nils O. Selåsdal"
2006-02-06 17:33 ` uriel
2006-02-06 17:37 ` Ronald G Minnich
2006-02-06 17:55 ` Lluís Batlle
2006-02-06 19:45 ` Russ Cox
2006-02-06 17:51 ` andrey mirtchovski
2006-02-06 19:49 ` Joel Salomon
2006-02-06 17:25 ` Ronald G Minnich [this message]
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=43E78698.9020103@lanl.gov \
--to=rminnich@lanl.gov \
--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).