| Bug #26774 | Crash on ARM platform even after REPAIR TABLE | ||
|---|---|---|---|
| Submitted: | 1 Mar 2007 22:16 | Modified: | 29 Oct 2007 16:41 |
| Reporter: | Christian Hammers (Silver Quality Contributor) (OCA) | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.32, 5.0.37 | OS: | Linux (Debian GNU/Linux etch) |
| Assigned to: | CPU Architecture: | ARM | |
| Tags: | qc | ||
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
[1 Mar 2007 22:18]
Christian Hammers
[29 Apr 2007 20:30]
[ name withheld ]
last mysql debugs between the last successfull command and the server crash
Attachment: crash.log (text/x-log), 4.00 KiB.
[29 Apr 2007 20:33]
[ name withheld ]
full mysql debugging logs from the lient startup
Attachment: full_crash.log.tar.gz (application/x-gzip, text), 127.99 KiB.
[29 Apr 2007 20:34]
[ name withheld ]
Compilation log
Attachment: compile_debug.log.gz (application/x-gzip, text), 137.84 KiB.
[29 Apr 2007 21:34]
[ name withheld ]
mysqld logs (probably more interesting). Complete log on request.
Attachment: crash_part_mysqld.log.gz (application/x-gzip, text), 17.16 KiB.
