New warnings/errors occurring after updating to 2.0.4.5

The #1400 refers to this issue:

It seemed to happen when reading files that we actively being changed.
Since the file shown is the transaction journal for the backup, I think this is the case as well.