This sequence causes the same errors:
ALTER TABLE postsearch DISABLE KEYS;
delete from postsearch where postId=65031 limit 1;
ALTER TABLE postsearch ENABLE KEYS;
#1034 - Incorrect key file for table: 'postsearch'. Try to repair it
Could this be a bug, as hinted at here by people using 4.1:
http://b
gerald_clark wrote:
Hardware?
Celeron 1.3Ghz, IDE drive, 512Mb RAM
OS and version?
GNU/Linux, 2.4.20-8 kernel
MySql version?
4.0.17
Size of data file?
Size of index file?
postsearch.frm 8.7K
postsearch.MYD 3.5G
postsearch.MYI 1.0G
postsearch.TMD 3.5G
Filesystem type?
ext3
Sorry 'bout that!
Also,
Hardware?
OS and version?
MySql version?
Size of data file?
Size of index file?
Filesystem type?
Jim Nachlin wrote:
I have a table with several keys. When I try to delete anything from
this table, I get data corruption and have to repair it with
myisamchk. Selects, updates work fine.
Here's th
Andrew Iles wrote:
Is this the true behavior or does it just appear to work this way? And if
so, is there any way to force MySQL to automatically save data to disk in a
way that is chronologically correct? This would make it much easier for me
to recover from an unexpected crash.
What os/vers
Use
mysqladmin shutdown
to stop the server.
You should have run myisamchk to fix the tables.
When you copied the tables from backup you probably changed the user
and permissions.
Ransom wrote:
> I was updating a database and my database got corrupted ( I'm not sure
> what coused this) but eve
