Bug #1804 | Repair table, then rows are missing | ||
---|---|---|---|
Submitted: | 11 Nov 2003 6:52 | Modified: | 13 Dec 2003 13:05 |
Reporter: | ANDRE Cyril | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S1 (Critical) |
Version: | 4.0.15a | OS: | Linux (Linux Debian - kernel 2.4.20) |
Assigned to: | Michael Widenius | CPU Architecture: | Any |
[11 Nov 2003 6:52]
ANDRE Cyril
[11 Nov 2003 7:06]
Martin Mokrejs
Are those directories where database files are located soflinked under the datadir directory? If two links from $datadir point to same target directory with datafiles, then that's the reason why they are corrupted. Are your tables MyISAM type and compressed? If so, 4.0.14 and 4.0.15 has has a bug, so upgrade. Did you modify the tables or run myisamchk while mysqld was running? If so, you know you were supposed to shutdown mysqld first of to flush table cache first? Flush table cache a post : myisamchk -dvv /data/$table.MYI output.
[11 Nov 2003 7:47]
ANDRE Cyril
Thanks for your fast answer! *** Are those directories where database files are located soflinked under the datadir directory? If two links from $datadir point to same target directory with datafiles, then that's the reason why they are corrupted. *** My *.MYI, *.frm, *.MYD are in /home/mysql/my_DB/ I have indicated it in the my.cnf file without any links. Nevertheless maybe you want to talk about somethink else ? *** Are your tables MyISAM type and compressed? If so, 4.0.14 and 4.0.15 has has a bug, so upgrade. *** My tables are MyISAM table but not read-only, so they can't be compressed. *** Did you modify the tables or run myisamchk while mysqld was running? *** I don't modify the tables but I create new tables. Is-it a problem ? Best regards
[16 Nov 2003 5:14]
ANDRE Cyril
Can you help me please ?
[18 Nov 2003 9:11]
ANDRE Cyril
an idea?
[13 Dec 2003 13:05]
Michael Widenius
Sorry, but you haven't included enough information for us to know where the problem should be. Please spend a couple if minutes and read http://www.mysql.com/doc/en/Bug_reports.html In the case you get crashed tables, you should first ensure if this is becasue mysqld dies in the middle of some operation. If this is NOT the case, then you should be able to follow the instructions in the manual of how to generate at test case: http://www.mysql.com/doc/en/Reproduceable_test_case.html Note that this public systems is only meant for repeatable bugs. If you can't repeat it then you can either ask for help on the public MySQL email lists for help or consider buying MySQL support.