Bug #68837 InnoDB recovery does not handle "truncate", leaves corrupt table
Submitted: 2 Apr 2013 15:29 Modified: 22 Jul 2014 12:56
Reporter: Jörg Brühe Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.5.20 OS:Any
Assigned to: CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[2 Apr 2013 15:31] Jörg Brühe
Extract of the server log: voluntary crash and "truncate" table damage

Attachment: crash-truncate.log (application/octet-stream, text), 42.38 KiB.