List:General Discussion« Previous MessageNext Message »
From:Gerald Clark Date:June 13 2001 1:15pm
Subject:Re: table corrupt - cant/wont recover! Help!!
View as plain text  
I sounds like the data or index file may be getting larger than the 
maximum file size allowed by the operating/filesystem.

What operating system and kernel version are you using, and what file 
system?
How big are these files?

Rob wrote:

> One of my tables is corrupt and I tried all the usual ways to repair it but
> to no avail even when I restored the backup..
> 
> Tried this..
> 
> isamchk --recover --quick user_host
> isamchk --recover user_host
> isamchk --safe-recover user_host
> 
> All that happened is the last 30000 records were wiped out! Presumably these
> were the records added after the table became corrupt..
> 
> I then restored the backup and tried to regenerate the index file by 'delete
> from user_host' then copying the datafile back then again running the
> isamchk script but the same thing happened again and I'm short of 30,000
> records!
> 
> I get this after copying in the datafile and running isamchk..
> 
> isamchk --recover --quick user_host
> - check delete-chain
> - recovering ISAM-table 'user_host.ISM'
> Data records: 0
> - Fixing index 1
> Found block with impossible length 4291909395 at 3066686; Skipped
> ISAM-table 'user_host' is not fixed because of errors
> 
> Then this..
> 
> isamchk -e user_host
> Checking ISAM file: user_host
> Data records:     399   Deleted blocks:       0
> - check file-size
> isamchk: warning: Size of datafile is: 4751079        Should be: 0
> - check delete-chain
> - check index reference
> - check data record references index: 1
> isamchk: error: Can't read indexpage from filepos: 4294967295
> - check records and index references
> isamchk: error: Record at:          0  Can't find key for index:  1
> ISAM-table 'user_host' is corrupted
> Fix it using switch "-r" or "-o"
> 
> Then this..
> 
> isamchk --recover user_host
> - recovering ISAM-table 'user_host.ISM'
> Data records: 399
> - Fixing index 1
> Found block with impossible length 4291909395 at 3066686; Skipped
> Found block with impossible length 4291670648 at 3306401; Skipped
> Found block with impossible length 4291733906 at 3261315; Skipped
> Found block with impossible length 4290444869 at 4708862; Skipped
> Found block with impossible length 4292397516 at 3022877; Skipped
> Found block with impossible length 4292143085 at 4393951; Skipped
> Found block with impossible length 4292535130 at 4063247; Skipped
> Found block with impossible length 4292132143 at 4525679; Skipped
> Found block with impossible length 4292640444 at 4103477; Skipped
> Found block with impossible length 4292768094 at 3993416; Skipped
> Found block with impossible length 4292445422 at 4333022; Skipped
> Found block with impossible length 4292564259 at 4363626; Skipped
> Found block with impossible length 4293759359 at 3189457; Skipped
> Found block with impossible length 4292713373 at 4346539; Skipped
> Found block with impossible length 4293005338 at 4303407; Skipped
> Found block with impossible length 4294119730 at 3209555; Skipped
> Found block with impossible length 4293984724 at 3350649; Skipped
> Found block with impossible length 4293187792 at 4234130; Skipped
> Found block with impossible length 4292929131 at 4589936; Skipped
> Found block with impossible length 4294116382 at 3573433; Skipped
> Found block with impossible length 4294790559 at 2948858; Skipped
> Found block with impossible length 4294510876 at 3291167; Skipped
> - Fixing index 2
> Data records: 68935
> 
> 
> Anyone know what I can do or if its possible to fix this??
> 
> 
> thanks.
> 

-- 
Gerald L. Clark
gerald_clark@stripped

Thread
table corrupt - cant/wont recover! Help!!Rob13 Jun
  • Re: table corrupt - cant/wont recover! Help!!Gerald Clark13 Jun