| Bug #79674 | InnoDB table space corruption prevents MySQL server from starting | ||
|---|---|---|---|
| Submitted: | 16 Dec 2015 16:08 | Modified: | 17 Jul 2018 7:36 |
| Reporter: | Dennis Buteyn | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.5.46 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | corrupt, crash, innodb | ||
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:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[16 Dec 2015 16:09]
Dennis Buteyn
[16 Dec 2015 16:10]
Dennis Buteyn
Diagnostic utility output of the affected page
Attachment: page-1225.log (text/x-log), 286 bytes.
[20 Dec 2015 13:35]
Dennis Buteyn
Detailed output of all records on the affected page
Attachment: records.log (text/x-log), 92.02 KiB.
