List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:August 8 1999 2:25pm
Subject:3.22.24 Perpetual Database Corruption problems
View as plain text  
Hi!

>>>>> "Van" == Van  <vanboers@stripped> writes:

Van> I'd thought this had been resolved, but, I'm getting consistent
Van> corruption problems with one of my databases running 3.22.24.  

Van> +-------------+-------------+------+-----+---------------------+----------------+
Van> | Field       | Type        | Null | Key | Default             |
Van> Extra          |
Van> +-------------+-------------+------+-----+---------------------+----------------+
Van> | id          | int(10)     |      | PRI | 0                   |
Van> auto_increment |
Van> | date        | datetime    |      | MUL | 0000-00-00 00:00:00
Van> |                |
Van> | description | char(255)   |      |     |                    
Van> |                |
Van> | debit       | float(10,2) |      |     | 0.00               
Van> |                |
Van> | credit      | float(10,2) |      |     | 0.00               
Van> |                |
Van> | checkno     | int(11)     |      |     | 0                  
Van> |                |
Van> +-------------+-------------+------+-----+---------------------+----------------+
> 
Van> When doing an insert:
Van> INSERT INTO checking (id, date, description, debit, credit, checkno)
Van> VALUES ('', '1999-08-07 16:36:34', 'ACME Floppy Disks, INC.', '253.05',
Van> '', '440')
Van> I get the insert.

Did you do 'myisqladmin flush-tables' before doing isamchk.  If not,
then the following warning may be irrelevant.

Van> sedona:/home/www/nbd$ sudo isamchk -eR1,R2 /usr/local/var/nbd/checking
Van> - Sorting records in ISAM-table '/usr/local/var/nbd/checking.ISM'
Van> Data records:      414   Deleted:       0
Van> isamchk: error: 2 when reading datafile
Van> ISAM-table '/usr/local/var/nbd/checking' is not fixed because of errors
Van> Then, I do a 
Van>  mysqladmin -p flush-tables

Van> Then,
Van> sedona:/home/www/nbd$ sudo isamchk -r /usr/local/var/nbd/checking
Van> - recovering ISAM-table '/usr/local/var/nbd/checking.ISM'
Van> Data records: 414
Van> - Fixing index 1
Van> - Fixing index 2
Van> Data records: 413

Van> Then, I do the insert, and it works.  Doing an isamchk -eR1,R2 shows no
Van> errors.

Note that to check a table you should NOT use -R !  The -R repairs a
table.


Van> This happens consistently.  I've got a perpetually self-corrupting
Van> dbase, here.  Will an upgrade to 3.22.25 be a possible cure for this
Van> little beast?  Or, could someone else point me at another option.  I've
Van> replicated this dbase to other servers, dropped it entirely and
Van> recreated the checking.frm structure, then load data infile-ed it, but,
Van> same results.

Your tables are probably ok;  I would guess you are just using isamchk wrongly.
(Ie;  Using it without taking down the MySQL server).

Van> Thanks to anyone who can help me figure this out.

Regards,
Monty
Thread
Search engine for the web siteSheni R. Meledath7 Aug
  • Re: Search engine for the web siteThimble Smith7 Aug
  • 3.22.24 Perpetual Database Corruption problemsVan8 Aug
    • 3.22.24 Perpetual Database Corruption problemsMichael Widenius8 Aug
  • Error 2 (Was Re: 3.22.24 Perpetual Database Corruption problems)Van8 Aug
  • Re: 3.22.24 Perpetual Database Corruption problemsVan8 Aug
Re: Search engine for the web siteAndrey Muratov9 Aug