I've also found a problem with "myisamchk --sort-keys":
christopher:/var/lib/mysql/dmoz# myisamchk -rq xurls - check record delete-chain - recovering (with sort) MyISAM-table 'xurls' Data records: 1981904 - Fixing index 1 - Fixing index 2 - Fixing index 3 Data records: 4332227
christopher:/var/lib/mysql/dmoz# myisamchk -ce xurls Checking MyISAM file: xurls Data records: 4332227 Deleted blocks: 0 - check file-size - check record delete-chain - check key delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check data record references index: 3 - check records and index references
christopher:/var/lib/mysql/dmoz# myisamchk -aS xurls - Sorting index for MyISAM-table 'xurls'
christopher:/var/lib/mysql/dmoz# myisamchk -ce xurls
Checking MyISAM file: xurls
Data records: 4332227 Deleted blocks: 0
- check file-size
- check record delete-chain
- check key delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
myisamchk: error: Found key at page 208005120 that points to record outside datafile
- check records and index references
1307000^C
Also, I gt a segfault trying to use "myisamchk --sort-records".
Christopher L. Everett wrote:
I have an application where I create a faily large table (835MB) with a
fulltext index. One of our development workstations and our production
server will run the script to load the table, but afterwards we have a
pervasive corruption, with out of range index index pointer errors. Oddly, my development workstation doesn't have those problems.
My box and the ones having the problems have the following differences:
- my box runs ReiserFS, the problem boxes run XFS - my box has a nice SCSI HD subsystem, the problem boxes do IDE.
All three boxes run Linux 2.6.x kernels, and my workstation and production
server share the same mobo. Come to think of it, I saw similar corruption
issues under 2.4.x series kernels and MySQL v4.0.x, it just wasn't the
show stopper it is now.
Also, on all three boxes, altering the table to drop an index and create a new one requires a "myisamchk -rq" run afterwards when a fulltext index either exists or gets added or dropped, which I'd also call a bug.
-- Christopher L. Everett
Chief Technology Officer www.medbanner.com MedBanner, Inc. www.physemp.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
