Simon Boulet <[EMAIL PROTECTED]> writes: > Hi, > > This is a known issue with newer versions of GNU cp and Rsnapshot. > > http://sourceforge.net/mailarchive/forum.php?thread_id=8988105&forum_id=41320 > > Update to Rsnapshot 1.2.3.
Excellent info... thanks. It seems there should be some safeguard in place to prevent a change like this from allowing rsnapshot to eat its previously created backups. After installing the new cp, rsnapshot ate one full hourly.* every 4 hours until only hourly.0 remains by rming hourly.5 and moving hourly.* to hourly.5. And of course it won't copy hourly.0 to hourly.1 so hourly.0 isn't even renewed either. Within a few hours your relied upon backups have chewed themselves into oblivion. I've scripted something that writes a .SUCCESS file to my rsnapshot base each run so if it isn't found right before running rsnapshot, then rsnapshot isn't run. I'm surprised there wasn't some similar safeguard built into rsnapshot. -- gentoo-user@gentoo.org mailing list
