Hello,
On 25/10/2020 20:06, Guillermo Rozas wrote:
The script in the repo works by systematically comparing the full-file
MD5 checksum of the cpool files to their filename, flagging any
difference. Check the README for a bit more of detail, use options, and
advantages/disadvantages with respect to the built-in check option. Feel
free to raise issues and contribute!
Nice script there, thanks.
We have one question : what to do if/when the script detects a problem
on a pooled file ? Can we just delete the file (based on the -maybe
wrong- assumption it will be copied back on the next run) ?
An example of what we sometimes get :
Sat 31 Oct 03:47:01 CET 2020
/mnt/BackupPC/cpool/30
pigz: warning:
/mnt/BackupPC/cpool/30/24/3024a19df8965e84a1f5866ccd1927c8: trailing
junk was ignored
ZLIB/PIGZ ERROR: 3024a19df8965e84a1f5866ccd1927c8 ->
0af97176caed7c0152d8a5be1dd631e3
Tia,
--
B&A Consultants - Sécurité informatique - Conseils et audits
www.ba-consultants.fr
Tél : (0) 563 277 241 - Fax : (0) 567 737 829
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
