Hi! Ok, I finally managed to create a small test case that shows a bug with myisamchk -R on a table with fulltext-index and certain content in the table.

I found the bug in MySQL 4.0.10, binary rpm-version. I also tested on MySQL 3.23.55 (binary rpm), and the bug is also present in that version.

I'm running Red Hat Linux 8.0 MySQL 4.0.10-gamma. Binary RPM version. The machine is a dual P2, 400MHz 768 Mb RAM

How-to-repeat: DROP TABLE IF EXISTS usrProfileTable2; CREATE TABLE usrProfileTable2 ( usrName varchar(40) NOT NULL default '', music text, PRIMARY KEY (usrName), FULLTEXT KEY music (music) ) TYPE=MyISAM;

INSERT INTO usrProfileTable2 VALUES ('amrisen','jag gillar pop musik.'); INSERT INTO usrProfileTable2 VALUES ('amro','markolio'); INSERT INTO usrProfileTable2 VALUES ('Amy-Ery90','MP3/kPOP/kRB'); INSERT INTO usrProfileTable2 VALUES ('Amtil','E.M.M.A');

Shut down mysqld Running: myisamchk -R 1 /var/lib/mysql/kamrat/usrProfileTable2.MYI

...will give me: - Sorting records for MyISAM-table '/var/lib/mysql/kamrat/usrProfileTable2.MYI' Data records: 4 Deleted: 0 myisamchk: error: 126 when updating key-pointers MyISAM-table '/var/lib/mysql/kamrat/usrProfileTable2.MYI' is not fixed because of errors

And the table is corrupt...