Bug #52243 binlog_index.test fails with corrupted tables
Submitted: 20 Mar 2010 14:10 Modified: 22 Apr 2010 11:51
Reporter: Sergei Golubchik Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any

[20 Mar 2010 14:10] Sergei Golubchik
Description:
binlog_index.test when run together with other tests, not alone, fails with

binlog.binlog_index                      [ fail ]  Found warnings/errors in server log file!
...
100320 14:51:24 [ERROR] mysqld: Table './mysql/user' is marked as crashed and should be repaired
100320 14:51:24 [Warning] Checking table:   './mysql/user'
100320 14:51:24 [ERROR] 1 client is using or hasn't closed the table properly
Warnings:
Error   145     Table './mtr/test_suppressions' is marked as crashed and should be repaired
Error   1194    Table 'test_suppressions' is marked as crashed and should be repaired
Error   1034    1 client is using or hasn't closed the table properly
^ Found warnings in /usr/home/serg/Abk/mysql/5.2/mysql-test/var/log/mysqld.1.err

How to repeat:
.

Suggested fix:
add "flush tables" before the first crash
[20 Mar 2010 19:49] Valeriy Kravchuk
What exact set of tests should I run to get this specific failure?

"binlog_index binlog_index" fails for me on second test with 5.1.46 from bzr, but differently. "binlog_grant binlog_index" just works etc.
[20 Mar 2010 20:03] Sergei Golubchik
I don't know, debug or whatnot.

The test modifies tables (test_suppressions), then it crashes the server.
On restart it understandably complains that "1 client is using or hasn't closed the table properly". closing all tables before the crash helps.

I've already pushed the fix to mariadb 5.2.
[22 Mar 2010 11:51] Sveta Smirnova
See also bug #52002.
[22 Mar 2010 11:51] Sveta Smirnova
Sergei,

this is not repeatable for me as well. Which tests do you run together with binlog_index?
[22 Apr 2010 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".