As of June I get these errors in my backup log: gzip: stdin: warning: file timestamp out of range for gzip format Trouble zipping file, storing uncompressed I think the first line is the problem, the second is the backup (afio) responding. I checked my backup logs and the first time this came up (since 2015) is at the end of June on two f34 machines. For each file, afio asks gzip to compress it and deliver the result using a pipe back to afio which then appends it to the backup. What is the cause of this error? Is there really a file with a bad timestamp or does gzip have some issues? So far the only online mention I found is for an old logrotate problem. I should say that I am running the backup on a live (though quiescent) system I expect to encounter issues. - Above, I figure that afio still backs up the file, uncompressed, so not a big issue. - Another situation is when a file is updated while processing. This is a common issue with files that have data appended regularly, which produces a different error: gzip: stdin: file size changed while zipping which I understand and can live with. This is f34, fully updated. -- Eyal Lebedinsky (fedora@xxxxxxxxxxxxxx) _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
