hi Ged,
That's like saying your car shouldn't stop when all the coolant leaks out of the radiator. You had a temperature gauge. You were supposed to keep an eye on it. You failed to do that. Now, instead of a can of Radweld, you need a new engine. It's entirely your own fault.
so to be clear i use : - a filesystem with cow and checksuming - a maintenance tool that check the FS on a regular basis that scrub the complete fs in 6 weeks time max. ( a % each week ) - thats the case on the source and on the destination most of the time (some sources are in ext4 but less and less) - i monitor any errors to a zabbix server that alert me if there is any alerts on the FS side and not any alerts show up. I have seen some rsync crash mainly in OOM situations and network can fail too.
You seem to be asking BackupPC to be a filesystem repair tool. That's a completely different animal, way beyond the scope of a comparatively simple scheme for copying files, and unless the latest Pacific Bubble 'AI'[*] turns out to be more than a bubble there never will be any way in general, to repair a broken filesystem reliably and automatically.
not really. i dont ask anything special, i ask the community if there is a way, if we detect an issue, to tell backuppc to correct it :) -- cordialement, Ghislain ADNET. AQUEOS.
_______________________________________________ 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/
