metadata corruption

[gsmolk]

Introduced by: 66a1c64
Reported by: Leonid Kraubner
If backup_content.control file size is taking more than BLCKSZ*500 (usually 4000KB), then current line will not be added to backup_content.control file.
So we basically loose metadata about one file per 4000KB.
It means that all backups with lots of files taken by 2.1.4, 2.1.5 and 2.2.1 versions are corrupted.

What to do?

1. Upgrade as soon as you can to 2.2.3 version or newer and make new backups.
2. Run validate using fresh binary on all backups, it is capable of detecting metadata corruption introduced by this bug.

What to do if metadata corruption is detected?

1. It is still possible to restore CORRUPT backup to evaluate the situation using --force flag. Restored instance can be verified using checkdb command with --amcheck flag.
2. Tool for metadata synchronization will be provided shortly

[gsmolk]

Fixed in 251fc83
Release: 2.2.3