Paul Mantz wrote at about 10:19:45 -0800 on Thursday, December 18, 2008:
 > Hello Thomas,
 > 
 > Did the BackupPC_nightly jobs take 22 hours on the 17th as well?  If
 > they didn't, I would suspect that since you restored the TopDir from a
 > tarball, that the hardlinking wasn't handled correctly in the tar
 > compression.  BackupPC_nightly would have been re-establishing the
 > de-duplication between the pc/ and pool/ directories all in one go,
 > which could reasonably take that long.
 > 

I don't think that BackupPC_nightly checks for hard link dups between
the pc/ and pool/ directories. I believe that it only checks for pool
files with nlink=1 (which are deleted) and for "chains" that need to
be renumbered due to holes in the numbering. (also weekly, it updates
the backupInfo files and deletes old logs). Unless there is a bug in
the code or filesystem issues, it's hard to see what would cause such
a relatively "simple" and "linear" routine to bog down like that.

In fact, the whole reason I had to write my BackupPC_fixLinks.pl
routine was to fix the various cases of pool duplications and missing
links between pc/ and pool/






------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
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/