Bug #24133 CHECK TABLE with concurrent INSERT can reset auto_increment also in 4.1.21
Submitted: 9 Nov 2006 9:44 Modified: 3 Dec 2006 9:03
Reporter: Borislav Ivanov Email Updates:
Status: won't fix Impact on me:
None 
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:4.1-BK, 4.1.22, 4.1.21 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[9 Nov 2006 9:44] Borislav Ivanov 
Description:
I found that Bug#19604 also occures in 4.1.21 version.

I've checked the source code of myisam/mi_check.c and it was the same as in 5.0* before applying the patch from http://lists.mysql.com/commits/7076.

How to repeat:
The script of Ingo Strüwing from Bug#19604 

Suggested fix:
Applying similar patch to 4.1 version
[27 Nov 2006 14:59] Valeriy Kravchuk 
Thank you for a problem report, and sorry for a delay with its processing. Please, try to repeat with a newer version, 4.1.22, and inform about the results.
[28 Nov 2006 11:00] Borislav Ivanov 
The problem occured on a production server, but I'll try to reproduce the same situation on a test one. I'll get back with results. I also checked the source of 4.1.22 but I haven't found changes in myisam/mi_check.c similar to those in 5.0 version.
[28 Nov 2006 16:43] Borislav Ivanov 
I've just run a test using modified version of script by Ingo Strüwing in Bug#19604. I've run it on version 4.1.22 (mysql-standard-4.1.22-pc-linux-gnu-i686.tar.gz). I'll attatch the script along with script results. If you check file bug19604-1.log at line 16936, it says "warning Auto-increment value: 0 is smaller than max used value: 196088", witch indicates that bug appeared.
[28 Nov 2006 16:44] Borislav Ivanov 
Here is the script with result data.

Attachment: bug-24133.tar.gz (application/x-gzip, text), 18.43 KiB.