From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 18 Jun 2008 22:50:37 +0200 From: Enrico Weigelt To: 9fans@9fans.net Message-ID: <20080618205037.GA14826@nibiru.local> References: <20080618193533.GA23589@nibiru.local> <20080618201548.88DE21E8C1F@holo.morphisms.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080618201548.88DE21E8C1F@holo.morphisms.net> User-Agent: Mutt/1.4.1i Subject: Re: [9fans] Ideas for gc on venti Topicbox-Message-UUID: c21989fa-ead3-11e9-9d60-3106f5b1d025 * Russ Cox wrote: Hi, > The greatest strength of venti, and also of > the worm file system, is that once data is written, > those disk blocks are never changed again. Yep, but my scenario is not completely worm. Some data might be removed/unused. Even it might not be absolutely necessary, it would be nice to reclaim space. > Why not just use an ordinary file system? > What benefit are you deriving from using venti > that is making all this rewriting worthwhile? Venti makes lots of things easier, eg. it avoids duplicated data. For example, if some users upload already existing media, I've just got one more db record, but no duplicate data. Doing this on fs basis would require more logic on application side. Another, very important, point is that I'm creating an cloud venti, which synchronizes with its peers on-demand and distributes the data over the cloud. So I don't need additional logic for clustering the application / it's data spaces. (I'll also use the venticloud for several other things, eg. for building an distributed fs or something like S3 on it). cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ cellphone: +49 174 7066481 email: info@metux.de skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------