Had this problem happen again, same large VMDK file. Last time that VMDK was modified was a few days ago, and several backups completed successfully since. It’s puzzling that this error just “decides” to pop up later.
Is the size discrepancy 32 KiB (32768) again? Does that mean anything in terms of --blocksize etc.?
Pretty much all I have for other troubleshooting advice is what’s already been given for prior situation.
Yep, it’s exactly 32 KiB off. My blocksize and related options are set at the default.
Troubleshooting the database is beyond my abilities, but I am willing to share it with a dev that has the time to dig into this.