gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: Re: [Gzz-commits] manuscripts/storm article.rst
Date: Mon, 27 Jan 2003 22:14:38 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9

address@hidden wrote:
Quoting Benja Fallenstein <address@hidden>:


CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>        03/01/25 12:51:34

Modified files:
storm : article.rst
Log message:
        bit




2. Block storage
================
+
+In our system, Storm (for *storage module*), all data is stored
+in *blocks*, byte sequences identified by a
+cryptographic hash. Blocks often have a similar granularity
+as files, but they are immutable, since any change to the
+byte sequence would change the hash (and thus create a different block).

Hmm, perhaps we should make a reference to CFS/PAST in this specific part: If
these system somehow differs, we should explain how. If not, tell that 'they are
very similar etc'.

Go ahead :-)

Btw, how Storm blocks are shared among computers ? Is it more like CFS or
PAST(CFS: files are splitted to blocks (merkle-style), PAST: share whole files)

We share whole "files" (Storm blocks).

? Or is Storm more like decentralized index, which has 'pointer references' to
blocks: find computer which points to another computer, which hosts the actual
block ( first block would be a dummy block, e.g. record of hash and ip 
address.) ?

Either approach is possible. Probably the approach where the DHT holds the ips of computers that have the block will be implemented first.

-b.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]