I can repeat steps 2-5 multiple times without a problem. I just did it 14 times without an error. Then, suddenly, on the 15th run, I get…
InnoDB: Page [page id: space=0, page number=5] log sequence number 3107477 is in the future! Current system log sequence number 3107475. InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22.2 Forcing InnoDB Recovery for information about forcing recovery.
The server is a 48-core Dell PowerEdge R640 with 1TB RAM and 6 x NVME drives. There is no load on the server as it is not yet in production. The symptom is reproducible. If I run the backup several times in a row, it will eventually error out after 3 or 4 runs, but I have seen it go as many as 40 consecutive runs before throwing the error.
I checked it again, and yes. It broke in the same place. I ran the process 31 consecutive times, and on the 32nd try it threw error message…
InnoDB: Page [page id: space=0, page number=5] log sequence number 3284271 is in the future! Current system log sequence number 3284268.
InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to MySQL :: MySQL 5.7 Reference Manual :: 14.22.2 Forcing InnoDB Recovery for information about forcing reco