On Wed, Apr 16, 2008 at 02:52:34PM +0200, Ludovic Drolez wrote: > > > And what about a mix of the two ? > > > - keep hard links for files less than the chunk size (filenames begin > > > with an 'f' as before) > > > - for files bigger than the chunk size, create a regular file which > > > contains references to the chunks in the cpool (the files could begin > > > with an 'r' for example). > > > > The main problem is that you cannot tell anymore whether a file(chunk) > > in the pool is still needed or not. You'd need to look into every backup > > and check if there's still a reference to that chunk. > > then, instead of the 'r' file containing the references to the chunks, > simply create a 'r' directory, which will contain hard links to the > chunks, so that cpool chunks are still referenced as before !
While it would work (and I thought about that myself), I'm not keen on having even more directories in the BackupPC file system. We're talking about hundreds of thousands of *additional* files here, if the chunk size is, say 64k. The File::Rsync stuff would need rewriting though (but I'm no developer, I'm just guessing). Tino. -- „What we resist, persists.” (Zen saying) www.craniosacralzentrum.de www.forteego.de ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ BackupPC-devel mailing list BackupPC-devel@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
