MySQL Bugs: #63474: MySQL abort as accessing I

Bug #63474	MySQL abort as accessing I_S of truncated table
Submitted:	29 Nov 2011 14:49	Modified:	12 Jan 2012 15:42
Reporter:	liu hickey (OCA)	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S2 (Serious)
Version:	5.1.48/5.1.53	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	Abort, page no missing, truncate table

Description:
This is an old problem, please refer to attached error log. You could also refer to http://bugs.mysql.com/bug.php?id=54220  for more information, or http://bugs.mysql.com/bug.php?id=54678 of the deeper analyze.

We hit this bug in MySQL-5.1.48, but it's fixed in MySQL-5.1.53. Unfortunately, it's still failed in our testcase which provides a more stress test for MySQL-5.1.53 though this bug is no longer exist. While in latest MySQL-5.1.59, it's not repeatable but with too many other changes that wipe out this bug. So from this sense, the patch for MySQL-5.1.53 is not fixed for this bug. The detail patch is http://bugs.mysql.com/bug.php?id=57700.

How to repeat:
Run the test case provided (run start.sh, some path might be modified for you environment, but it's very simple to do it).

Remember it's for innodb_file_per_table=ON and with innodb-plugin.

Suggested fix:
Revert the dict_table_x_lock_indexes to the line before " if (table->space && !table->dir_path_of_temp_table) { ", that lock all indexes before discard tablespace and release these locks after recreate tablespace in row_mysql_lock_data_dictionary.

error log

Attachment: sns_tablespace_discard_err.log (application/octet-stream, text), 21.86 KiB.

start.sh

Attachment: mut_thr.rar (application/octet-stream, text), 888 bytes.

Thank you for the report.

I can not repeat described behaviour.

Please try with current version 5.1.60 and if problem still exists send us MySQL package name you use (file name you downloaded from our website) and configuration file.

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".