Bug #27872 Incorrect error message when disk fills up running a large query against a view
| Submitted: | 17 Apr 2007 6:26 | Modified: | 27 Sep 2007 8:36 |
|---|---|---|---|
| Reporter: | Joseph Libson | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 5.0.37-community-log | OS: | Linux |
| Assigned to: | CPU Architecture: | Any |
[17 Apr 2007 6:26]
Joseph Libson
[17 Apr 2007 11:59]
MySQL Verification Team
Thank you for the bug report. mysql> insert into tbg (name) select name from tbg; ERROR 126 (HY000): Incorrect key file for table 'e:\tmp\#sql_8e0_0.MYI'; try to repair it mysql>
[17 Apr 2007 13:07]
Joseph Libson
And just to be clear. The table that I was selecting against was an Innodb table. So the whole "repair" thing is not applicable anyway.
[9 Aug 2007 22:22]
Sveta Smirnova
Bug #28363 was marked as duplicate of this one.
[10 Jan 2008 2:48]
aaron brick
this one is a pain in the ass! please upgrade severity!
[11 Mar 2011 9:16]
Daniƫl van Eeden
I can confirm that it's still an issue with 5.5.8. Creating an index on a large InnoDB table returns this error: ERROR 1034 (HY000): Incorrect key file for table 'test001'; try to repair it You could see that it's an space issue if you watch /tmp. I would suggest to change the severity to S2 as this could break replication easily. 1. The error should indicate possible issues with tmpdir. 2. For InnoDB it shouldn't suggest a repair.
[24 Apr 2020 13:10]
MySQL Verification Team
This bug has a duplicate in the following one: https://bugs.mysql.com/bug.php?id=99293
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.