On 3/2/2010 2:12 AM, Jeffrey J. Kosowsky wrote:
>
> One more question if you don't mind...
> Can you give an outline of how expiry works in the absence of
> hard-links? Specifically, without walking through the whole pc tree
> each night and tabulating all the md5sum references, how do you know
> when a pool file no longer has any remaining pc-tree references and
> therefore can be deleted from the pool? And if you do walk through the
> pool, can you do anything better than an O(n log n) type sort of the
> resulting md5sum lists that you would presumably construct?

I think this will need some sort of atomic-operation reference count 
manager at the heart of things so you don't do those lookups except as a 
repair step.

Will there be a way to disable the de-dup operations completely in the 
case where the underlying filesystem does it at the block level?  I'd 
expect such filesystems to become common and stable within the life of 
this backuppc version.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/