Brian, the testcase is to backup some TB of data, and try to read them, the index should not be corrupted. This is why I'm asking upstream to test the package once its in proposed pocket, because I lack the data to test it properly
** Description changed: [ Impact ] * Data is corrupted on some specific conditions [ Regression Potential ] * Really low, the package has an autopkgtestsuite that runs thousand of tests, and the fix is since one year part of upstream code + + [ Test Case ] + * Backup some TB of data, and try to read the index, it should be not corrupted [ Other info ] Per the "important notes" section of the borg docs: https://borgbackup.readthedocs.io/en/stable/changes.html "Pre-1.1.11 potential index corruption / data loss issue A bug was discovered in our hashtable code, see issue #4829. The code is used for the client-side chunks cache and the server-side repo index. Although borg uses the hashtables very heavily, the index corruption did not happen too frequently, because it needed specific conditions to happen. Data loss required even more specific conditions, so it should be rare (and also detectable via borg check). [..]" Theoretically affects all Ubuntu releases before 20.04 (focal.) I know this is a universe package, but if anyone was up for an SRU that would be fantastic.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877844 Title: [SRU] data corruption issue in all versions before 1.1.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1877844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
