myisam_block_size set to 4K corrupts indexes

[David Lombardi]

I was trying to play with server tuning parameters when I ran into a problem with myisam_block_size.

I changed the setting to 4096, restarted MySQL and recreated all the tables (except those in the MYSQL database that I always copy from the distribution).

The very first attempt to insert a row in a table of mine (that has an auto-inc primary key, plus another two indexes) fails with 'cannot insert duplicate key...' (error 126) and afterwards the table indexes are corrupted.
Running CHECK TABLE returns that
1) Table is marked as crashed
2) Found key at page 4096 that points to record outside datafile.
3) Corrupt

When the tables are created all report an index size of 4K, on the first insert attempt (that fails) the index file size jumps to 16K.

TIA.

David

Environment: Windows 2K3 Server, Mysql 5.0.19-nt



Edited 1 time(s). Last edit at 04/13/2006 01:42AM by David Lombardi.