Bug #31305 myisam tables crash when they are near capacity
Submitted: 30 Sep 2007 16:08 Modified: 26 Nov 2007 19:00
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:4.0.26, 4.1.21, 5.1.23, 5.0.48, 6.0.4 OS:Any
Assigned to: Alexey Botchkov CPU Architecture:Any
Tags: bfsm_2007_10_18, corruption, myisam

File: Maximum allowed size is 3MB.

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-31305.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

[30 Sep 2007 16:11] Shane Bester
paste into client. 5.0.45 and 5.1.23 cause corruptions.

Attachment: bug31305_testcase.sql (application/octet-stream, text), 118.25 KiB.