ok. i'm repairing a mysql table with 15,000,000 records. it is a little over a gig (1.052gb). i ran 'repair table `name`' about two days ago after a system crash, and it's still sitting there. here is top output

op - 05:01:03 up 2 days, 11 min, 7 users, load average: 170.99, 170.83, 170.08
Tasks: 226 total, 1 running, 225 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3% us, 0.0% sy, 0.0% ni, 0.0% id, 99.7% wa, 0.0% hi, 0.0% si
Mem: 906744k total, 902804k used, 3940k free, 4148k buffers
Swap: 0k total, 0k used, 0k free, 816388k cached


ok... HIGH load . the mysql database exists on a single 40gb SATA Raptor hard disk which is plugged directly into motherboard sata connector. as you can see the system has 1 gig memory. it's a p4 2.4ghz 800fsb cpu/motherboard. it's well cooled and healthy. i haven't had any hardware problems with it at all..

please, can anybody tell me if this is the expected result? how long should i expect to be waiting?

thanks,
oliver

Is it possible to select a small result set from the table, restore that to another table, and run a repair on it.

For example, run a repair on a 10,000 record table with similiar information, and see how long it takes. Then just do the math to get an estimate on how long a 15M record repair *should* take.

...

Then double it! just kidding