Hi,

Les Mikesell wrote on 2008-09-08 12:40:38 -0500 [Re: [BackupPC-users] fsck of 
/var/lib/backuppc]:
> Rob Owens wrote:
> > 
> > My concern was that if a file got corrupted, would BackupPC notice or
> > would it allow new files to be hardlinked to the corrupted files in the
> > pool.  I guess a full backup would take care of that, though.  Anyway,
> > thanks for the advice.  Looks like everything's working now.
> 
> I think the hashed filename in the pool is just a quick initial check 
> for possible matches and there is a full data comparison before new 
> files would be replaced with links.

I can confirm that. It's not actually "replaced" for existing files in the
pool. If candidates exists, no file is created until it is determined that
none of them match. If one matches (which is determined by a full comparison)
a link is created. For identical *new* files in one (or multiple concurrent)
backup(s), i.e. files not already in the pool, several instances are created
and then made to links to one of them in the BackupPC_link phase. I believe
that would again entail a full comparison, but I'm not sure right now.

The point is: corruption of pool files will *not* affect future backups.

Regards,
Holger

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/