On Fri, 2022-05-20 at 18:20 -0700, Gordon Messmer wrote: > On 5/20/22 14:15, Patrick O'Callaghan wrote: > > Thanks, but it's a desktop and the issue appears to be related to > > the > > latest version of Borg. The check errors happen across all of my > > existing backups, not just one. > > > As a result of deduplication, it's expected that all (or most) of > your > backups will share blocks of data. If there's corruption in the > backup > data, it is not surprising that it would affect all of them and not > just > one. > > Don't assume that the current version is broken. You've dismissed > https://github.com/borgbackup/borg/issues/6687 several times for > dubious > reasons. The conversation there included numerous troubleshooting > steps, and I suggest you go through all of them. If you still have > problems, collect a log of all of the commands you've run and the > output > they provided, and add that to a bug report. I haven't "dismissed" anything. The significant point is that these errors only appeared on upgrading to 1.2. I'm watching that bug thread and will add to it if I can say something useful. However I'll take your point about trying the troubleshooting steps. I haven't done so to date as my experience with Borg is limited. poc _______________________________________________ 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
