MySQL Bugs: #67960: innodb_ft_user_stopword_table becomes corrupt, causes server crash

Bug #67960	innodb_ft_user_stopword_table becomes corrupt, causes server crash
Submitted:	21 Dec 2012 17:08	Modified:	12 Apr 2013 12:28
Reporter:	Kolbe Kegel	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.6.9	OS:	Any
Assigned to:	Jimmy Yang	CPU Architecture:	Any
Tags:	crash, fulltext, innodb

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

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:

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

bt full from 5.6.9 on Linux, SIGABRT during OPTIMIZE TABLE

Attachment: gdb.txt (text/plain), 24.47 KiB.

sample testcase....

Attachment: bug67960.php (application/octet-stream, text), 1.37 KiB.