Kenn
Thu 14th Sep '00, 12:03am
Earlier we were having problems with session.ISM corrupting all the time, but after following directions on one of these boards, and recreating that table, that stopped happening. Now however, we are getting very frequent corruption errors in post and threads tables.
When this happens, one our more of the forums lose all but a few threads until I repair the database with isamchk (-r or -o options)
Here's the output of an isamchk post.ISM command
isamchk post.ISM
Checking ISAM file: post.ISM
Data records: 174937 Deleted blocks: 0
- check file-size
- check delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
isamchk: error: Found key at page 2670592 that points to record outside datafile
- check record links
isamchk: error: Keypointers and records dosen't match
ISAM-table 'post.ISM' is corrupted
Fix it using switch "-r" or "-o"
After running isamchk -r, this error doesn't show up, and all the missing threads come back, but it generally happens again within a couple of hours.
Does anyone have any suggestions about what might be causing this? I don't think it is constrained to really active times, and the server and mysql seem to be staying up through the error.
When this happens, one our more of the forums lose all but a few threads until I repair the database with isamchk (-r or -o options)
Here's the output of an isamchk post.ISM command
isamchk post.ISM
Checking ISAM file: post.ISM
Data records: 174937 Deleted blocks: 0
- check file-size
- check delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
isamchk: error: Found key at page 2670592 that points to record outside datafile
- check record links
isamchk: error: Keypointers and records dosen't match
ISAM-table 'post.ISM' is corrupted
Fix it using switch "-r" or "-o"
After running isamchk -r, this error doesn't show up, and all the missing threads come back, but it generally happens again within a couple of hours.
Does anyone have any suggestions about what might be causing this? I don't think it is constrained to really active times, and the server and mysql seem to be staying up through the error.