MySQL Bugs: #65750: mysql version 5.5.25 not dropping table when it is configured m/c is in use

Bug #65750	mysql version 5.5.25 not dropping table when it is configured m/c is in use
Submitted:	27 Jun 2012 11:51	Modified:	4 Aug 2012 7:25
Reporter:	shalini P S	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: DDL	Severity:	S2 (Serious)
Version:	5.5.25	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
Unable to drop drop the table when it is configured to my  linux m/c which is in use, able to drop only when my linux m/c is stopped

How to repeat:
Try configuring the db to ur m/c and drop table manually

Thank you for the report.

But what is "linux m/c"? Is it GNU Midnight Commander?

If it is really GNU Midnight Commander, please, check, if GNU Midnight Commander  used to list MySQL data directory in same time when you call DROP TABLE.

Thank you for the feedback.

So what is this? What do you mean by " when my linux m/c is stopped"?

Thank you for the feedback.

I can not answer you in hidden comments, because you would not see my answers. Thought we don't discuss anything confidential yet.

What we need is exact steps to repeat error: DROP TABLE failure. I still don't understand what you are doing.

Please, check if this manual page, http://dev.mysql.com/doc/refman/5.5/en/metadata-locking.html, explains why you can not DROP table (I assume it is used in active transactions while your application is running).

Please, send the output of

show full processlist;
show engine innodb status\G

taken at the moment when your application runs and you are trying to DROP the table.

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