List:General Discussion« Previous MessageNext Message »
From:MASSIMO PETRINI Date:August 2 2007 2:28pm
Subject:startup problem on mysql 5.0.45
View as plain text  
After a shutdown regular on my mysql master,  when the mysql process startup apper the
error below
 
----------------
070802 16:07:08 [Warning] The syntax for replication startup options is deprecat
ed and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
070802 16:07:10  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070802 16:07:11  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 31 1653757185.
InnoDB: Doing recovery: scanned up to log sequence number 31 1653757205
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 0 864831488
InnoDB: Last MySQL binlog file position 0 624186576, file name .\morisot-bin.000
184
InnoDB: Starting in background the rollback of uncommitted transactions
InnoDB: Cleaning up trx with id 0 864830109
070802 16:07:11InnoDB: Assertion failure in thread 3856 in file .\fsp\fsp0fsp.c
line 3204
InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page
_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 1472 stopped in file .\os\os0thread.c line 122
InnoDB: Thread 2752 stopped in file .\os\os0sync.c line 532

If I add in my.ini the words

innodb_force_recovery =3
mysql start in read only  mode, but with the possibility to execute a global dump. But the
dump file are correct (there are 4 innodb dbs)? How it is possible to define in which
table of the unique dump file there is the error ?  

Many thanks in advance


Massimo

Someboby can help to find which is the problem ? 
Thread
startup problem on mysql 5.0.45MASSIMO PETRINI2 Aug