Home » Performance » MySQL » repair table returns cryptic message
icon5.gif  repair table returns cryptic message [message #1114] Wed, 18 April 2007 23:33 Go to next message
mysqlNewDBA
Messages: 4
Registered: April 2007
Junior Member
I have an MyIsam table (> 1.5GB big) that crushes quite often. Repair table or myisamchk -r returns messages similar to the following:

Key 1 - Found wrong stored record at 973620836
Found link that points at 3546642079552990793 (outside data file) at 973620852
Found block with too small length at 973620868; Skipped

what does that mean?


some times i get the error message

Wrong bytesec: 32- 32- 32 at 662630684; Skipped

what does that mean?

server version: 5.0.22-Debian_0ubuntu6.06.2-log
2 dual core amd opteron processors @ 2Ghz
8GB Ram
supports large files
Re: repair table returns cryptic message [message #1120 is a reply to message #1114 ] Fri, 20 April 2007 18:11 Go to previous messageGo to next message
Peter  is currently offline Peter
Messages: 405
Registered: August 2006
Senior Member
Super Guru
First I should note I hope you do not run myisamchk while server is running as it can crash it even more. REPAIR TABLE should be used in this case.

Upgrade to last 5.0 version as were were some MyISAM corruption bugs fixed.

Now the error message says there is a pointer inside the file which points to too large offset (more than file length) and there is also dynamic record which length is too small to be correct so it is skipped.

Last one basically means wrong (unexpected) byte sequence which causes row to be skipped.


Peter Zaitsev, MySQL Performance Expert
MySQL Performance Blog - http://www.mysqlperformanceblog.com
MySQL Consulting http://www.mysqlperformanceblog.com/mysql-consulting/
Re: repair table returns cryptic message [message #1153 is a reply to message #1114 ] Wed, 25 April 2007 17:09 Go to previous message
mysqlNewDBA
Messages: 4
Registered: April 2007
Junior Member
Hey thanks for the explanation.
I hope upgrading my server will take care of some of these daily table corruptions am experiencing!
Previous Topic:slow query w/ an inner join
Next Topic:Optimize query with indexes all over the place
Goto Forum:
  


Current Time: Fri Jul 10 02:24:25 EDT 2009

Total time taken to generate the page: 0.03738 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 2.7.7.
Copyright ©2001-2007 FUD Forum Bulletin Board Software

MySQL is a trademark of Sun Microsystems.
InnoDB is a trademark of Oracle Corp.

Percona Performance Forums are a service of Percona, Inc.
Not affiliated with Sun Microsystems or Oracle Corp.