My base pool/cpool directory is on its own filesystem, and that hard
drive has a few bad sectors. It looks like those bad sectors are being
used by some cpool files. I will be replacing this hard drive soon,
and am extracting the old filesystem with ddrescue.

Would it be a bad idea to dump the ddrescue'd image to the new drive
and continue from there?

Basically what I am asking is, if a cpool file is corrupt will new
backups detect this and make a new file in the pool and not link to
the old cpool file, or will the new files being backed up be compared
to the hash of the old cpool file before it became corrupted and be
linked with the corrupted cpool file?

As long as new backups are fine I do not think it matters much that
the old ones are corrupted, if I need to restore them I have offsite
archive files.

I just don't want to have to start over with a completely empty list
of backups, and start over from backup # 0 (for naming collisions with
old offsite archives).

Any help would be appreciated, thanks.

-Justin Guenther

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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/