On reload you can lose some chunks that were in-transit, i.e. during a replication.
chunkserver: random chunk errors on restart
Chunk loss on unclean shutdown of master during changes
restarting master may cause read errors
New undergoal chunks while chunkserver is down
So we have two affected files, and also two choices.
1) Deleting them
This is where you restore your backup :-)
2) Erasing the affected blocks
Note, we didn't *repair* anything here. I literally had it zero out the affected data.
Reasoning: I'd rather have *most* of that full backup around. Bacula is smart enough to pinpoint the errors, and hopefully I'm smart enough to get along with the rest of that backup.
The amount of data affected would be 640MB, out of a 199GB backup, so a little under 1%.
The overview page (Important messages) will still display the missing files until the next check loop has finished.
How to avoid this?
Lobby for software liability laws
Get a support contract
Force the authors to do regression and fault testing
Be prepared to pay for it.