| Bug #51023 | Mysql server crashes on SIGHUP and destroys InnoDB files | ||
|---|---|---|---|
| Submitted: | 9 Feb 2010 12:12 | Modified: | 10 Jan 2011 16:41 |
| Reporter: | Vsevolod Volkov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S1 (Critical) |
| Version: | 5.1.35-5.1.52 | OS: | FreeBSD (7.2-RELEASE, 8.0-RELEASE, 8.1-RELEASE) |
| Assigned to: | Davi Arnaut | CPU Architecture: | Any |
| Tags: | crash, HUP, ibd, 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
[11 Feb 2010 8:28]
Vsevolod Volkov
[19 Feb 2010 15:02]
Vsevolod Volkov
The beginning of errors.log just after crash.
Attachment: errors.log (application/octet-stream, text), 23.38 KiB.
[19 Feb 2010 15:05]
Vsevolod Volkov
Corrupted .ibd file:
Attachment: wp_posts.ibd (application/octet-stream, text), 3.34 KiB.
[8 Dec 2010 12:25]
Vasil Dimov
Experimental patch
Attachment: bug51023-1.diff (application/octet-stream, text), 5.20 KiB.
