[Repost, because I posted this before I had confirmed my subscription and I don't see it on lists.mysql.com, although I see later postings. My apologies if it hits the list twice.]

*

RH-7.0/i386, mysql client, server and devel 3.23.24-1 from RH rpms, mnogosearch 3.1.8 working on the databases.

The other day my machine crashed badly, just as if I had pressed the reset button, right in the middle of database operations. After that all database operations seem to work fine anyway, but I have the following problem:

#myisamchk /path/to/tables/*.MYI myisamchk: error: 22 when opening MyISAM-table '/path/to/tables/dict.MYI' myisamchk: error: 22 when opening MyISAM-table (long list follows)

Hmm.

#perror 22 Invalid argument

OK, but which argument is invald? Who gave it to whom?

#tail /var/log/mysqld.log [nothing relevant]

Grr. Let's try something else.

#myisampack -t /path/to/tables/* /path/to/tables/dict.MYD gave error 126 on open /path/to/tables/dict.MYI gave error 22 on open /path/to/tables/dict.frm gave error 126 on open (and so on)

#perror 126 Index file is crashed / Wrong file format

Do I trust perror for accuracy on MySQL error mesages? I think I don't. All database operations work fine, so anything that's crashed can't be that bad.

Still, what do I do with myisamchk's refusal to work? An extensive search of the documentation, the mailing list and Altavista has made me none the wiser.

Any ideas?

Z