MySQL Bugs: #30345: Can't create/write to file '#sql_eac

Bug #30345	Can't create/write to file '#sql_eac_0.MYD' (Errcode: 17) (1)
Submitted:	9 Aug 2007 20:44	Modified:	19 Dec 2009 19:20
Reporter:	Akeem Oriola	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.27, 5.0.74	OS:	Windows (WIN XP SP2)
Assigned to:		CPU Architecture:	Any

Description:
couldn't dunmp the database and executing query other that select queries

How to repeat:
try executing DESCRIBE tablename;
this error appears
Can't create/write to file '#sql_eac_0.MYD' (Errcode: 17)

Thank you for the report.

But version 5.0.27 is quite old. Please upgrade to current version 5.0.45, try with it and if you can repeat error issue query SHOW VARIABLES LIKE 'tmp%', check if these directoriess exist and not locked. If you still get same error please inform us about results of queries and examining of directories.

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

I have 5.0.45 installed and I get this error in lots of different places sporadically, including the shell and when dumping. In MySQL Query Browser 1.2.12 I cannot expand tables in the schemata panel and it gives that exact "could not write...errcode:17" description at the very bottom of the browser. I get "Could not fetch columns" at the same time under the selected table in the schemata panel. 

When I run the query I get two values, tmp_table_size = 18874368 and tmpdir = "C:/temp".

I could try installing a newer version on my development machine, but at the moment the production server is 5.0.

We received this error over the weekend on 5.0.74 so the bug is still there.

Please, check if the same problem happens with recent version, 5.0.86.

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