| Bug #41571 | MySQL segfaults after innodb recovery | ||
|---|---|---|---|
| Submitted: | 18 Dec 2008 0:15 | Modified: | 18 Jun 2010 22:57 |
| Reporter: | Thomas Keller | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.32-7etch8, r5.0.67, 5.0.74 | OS: | Any (Debian 4.0) |
| Assigned to: | CPU Architecture: | Any | |
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
[7 Jan 2009 9:51]
Shane Bester
[15 Jan 2009 13:25]
Thomas Keller
MySQL recovery crashlog
Attachment: mysql.err (application/octet-stream, text), 3.49 KiB.
[15 Jan 2009 14:53]
Thomas Keller
gdb bt full output of the recovery crash - here we go
Attachment: recovery_crash-bt_full.txt (text/plain), 12.80 KiB.
[16 Jan 2009 11:31]
Thomas Keller
Output of gdb bt full; mysql compiled only with UNIV_DEBUG
Attachment: bt-full.txt (text/plain), 8.56 KiB.
[16 Jan 2009 13:36]
Thomas Keller
Output of gdb bt full; all debug options disabled
Attachment: bt-full_w_o_debug.txt (text/plain), 8.11 KiB.
