Re: mysqldump crash after VS update

[Tim Rath]

OK, got something from the log:

2018-07-30 13:31:12 1620 InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 1869967971:657205070, should be 140:300079!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 300079.
InnoDB: You may have to recover from a backup.
2018-07-30 13:31:12 1620 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex (hex info here)
InnoDB: End of page dump

A bit more context: The user successfully got a dump of his db on Friday, July 27 but deleted it because it didn't have new entries since the previous one. We believe new entries were written over the weekend, but he got the error above during a dump on Monday, July 30 (and all subsequent attempts). I restored a snapshot of the vm that was taken on the night of July 29 to see if we could retrieve anything from it, but we got the same error on the same table. So, whatever the problem was happened over the weekend. The error log did not have any entries between the last successful dump and the error above (ie, no error at whatever time the corruption happened).

Thanks.