> // combining functionality that is logically distinct is
> // generally called unmodular, and a layering violation
> // in this particular senerio.
>
> i agree with the principle, but i'm not sure it applies in this
> case. what's described (at least the part before any "garbage"
> collection is
// combining functionality that is logically distinct is
// generally called unmodular, and a layering violation
// in this particular senerio.
i agree with the principle, but i'm not sure it applies in this
case. what's described (at least the part before any "garbage"
collection is done) is real
> RAID has some disadvantages, eg. you have to nail-down partition
> sizes and it's not trivial to resize or move around volumes.
you seem to be making a general claim about all storage
management solutions that i don't think can be backed
up.
as an example i have no rooting interest in, way back
> one legitimate reason is the liability of keeping a user's data
> long after any business arrangements for storing such data has
> expired. this applies to kenfs too.
this is a good point.
are there any fs that have mechanisms to help
apply data retention policy? if one does offline
backup, de
one legitimate reason is the liability of keeping a user's data
long after any business arrangements for storing such data has
expired. this applies to kenfs too.
On Wed, 18 Jun 2008 22:57:27 +0200 Enrico Weigelt <[EMAIL PROTECTED]> wrote:
> * erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> > it makes sense for the storage managment function to present an
> > idealized block device while hiding details like disk replacement
> > and redundency.
>
> Well, I i
* erik quanstrom <[EMAIL PROTECTED]> wrote:
> it makes sense for the storage managment function to present an
> idealized block device while hiding details like disk replacement
> and redundency.
Well, I intend to make venti the storage device itself
(eg. in form on an hw appliance ;-P). At this
* Russ Cox <[EMAIL PROTECTED]> 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 absolu
> Well, that's not yet any form of gc - just an smooth data moving
> from one volume to another - also good if you intend to take some
> disk offline in near future, w/o serious interruption.
> (The deprecated volume get emptier and emptier, and no new
> data is added.)
in the original venti pape
> What do you think about that approach ?
I think you will lose your data.
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.
That makes it virtually impossible to lose data
due to software or human errors. T
Hi folks,
as I'm using venti as storage backend for an media archive, where
content can be deleted (and probably will happen often enough),
I'm currently thinking about how an garbage collection could be
achived.
Let's assume the following premise:
* only a few well-known apps are writing to
11 matches
Mail list logo
