Bug #48469 when innodb tablespace is configured too small, crash and corruption!
Submitted: 2 Nov 2009 12:48 Modified: 18 Jun 2010 23:02
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.0.85, 5.1.40, 5.4.3 OS:Any
Assigned to: Satya B CPU Architecture:Any

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:

[2 Nov 2009 12:50] Shane Bester
import this into a clean tablespace

Attachment: bug48469_testcase.sql (application/unknown, text), 5.42 KiB.