Bug #1577 | Corruption of MyISAM table | ||
---|---|---|---|
Submitted: | 16 Oct 2003 11:13 | Modified: | 18 Dec 2003 15:13 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | mysql-4.1.1-alpha-nightly-20031012 | OS: | GNU/Linux (Intel) |
Assigned to: | CPU Architecture: | Any |
[16 Oct 2003 11:13]
[ name withheld ]
[17 Oct 2003 5:36]
[ name withheld ]
any delete queries (like "delete from table1 where id=3563" and "delete from table1 where id in (12345,234)") corrupt table. mysql> check table idx; +--------------+-------+----------+----------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+----------+ | testtest.idx | check | status | OK | +--------------+-------+----------+----------+ 1 row in set (9.51 sec) mysql> delete from idx where id in (535333,332122); ERROR 1034 (HY000): Incorrect key file for table: 'idx'; try to repair it mysql> check table idx; +--------------+-------+----------+-----------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+-----------------------------+ | testtest.idx | check | warning | Table is marked as crashed | | testtest.idx | check | error | Found 725291 keys of 725292 | | testtest.idx | check | error | Corrupt | +--------------+-------+----------+-----------------------------+ 3 rows in set (2.38 sec) mysql> repair table idx; +--------------+--------+----------+----------+ | Table | Op | Msg_type | Msg_text | +--------------+--------+----------+----------+ | testtest.idx | repair | status | OK | +--------------+--------+----------+----------+ 1 row in set (5 min 31.60 sec) mysql> check table idx; +--------------+-------+----------+-------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+-------------------------------------------------------------------+ | testtest.idx | check | error | Found key at page 88717312 that points to record outside datafile | | testtest.idx | check | error | Corrupt | +--------------+-------+----------+-------------------------------------------------------------------+ 2 rows in set (14.29 sec) ...... mysql> check table idx; +--------------+-------+----------+----------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+----------+ | testtest.idx | check | status | OK | +--------------+-------+----------+----------+ 1 row in set (9.87 sec) mysql> delete from idx where id=535333; ERROR 1034 (HY000): Incorrect key file for table: 'idx'; try to repair it mysql> check table idx; +--------------+-------+----------+-----------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+-----------------------------+ | testtest.idx | check | warning | Table is marked as crashed | | testtest.idx | check | error | Found 725290 keys of 725292 | | testtest.idx | check | error | Corrupt | +--------------+-------+----------+-----------------------------+ 3 rows in set (1.42 sec) mysql> repair table idx; +--------------+--------+----------+----------+ | Table | Op | Msg_type | Msg_text | +--------------+--------+----------+----------+ | testtest.idx | repair | status | OK | +--------------+--------+----------+----------+ 1 row in set (2 min 28.00 sec) mysql> check table idx; +--------------+-------+----------+-------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +--------------+-------+----------+-------------------------------------------------------------------+ | testtest.idx | check | error | Found key at page 88717312 that points to record outside datafile | | testtest.idx | check | error | Corrupt | +--------------+-------+----------+-------------------------------------------------------------------+ 2 rows in set (5.55 sec)
[22 Oct 2003 12:41]
Dean Ellis
I am unable to duplicate this with the latest 4.1.1 BitKeeper sources (current as of today). All of the reported DELETE forms are functioning correctly. This was possibly a problem that has been corrected. Please try it with the latest sources and see if any of the DELETEs result in corruption. Thank you
[27 Oct 2003 5:29]
[ name withheld ]
4.1.1-alpha-nightly-20031026 snapshot still have this bug.
[18 Nov 2003 15:13]
Dean Ellis
I am still unable to duplicate this. Would it be possible for you to compress your tables and upload them to: ftp://support.mysql.com/pub/mysql/secret with a file name mentioning bug1577, so that we can test against your exact data?
[14 Feb 2005 22:54]
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".