MySQL Bugs: #9895: Synopsis

Bug #9895	Synopsis
Submitted:	14 Apr 2005 10:31	Modified:	14 Apr 2005 10:55
Reporter:	İSMAİL KILBÜKER	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S4 (Feature request)
Version:		OS:	Windows (Win XP)
Assigned to:		CPU Architecture:	Any

Description:
C:\mysql\bin>mysqld-nt --innodb_force_recovery=4 --console
050414 13:29:16  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 3237920
InnoDB: Doing recovery: scanned up to log sequence number 0 3237920
050414 13:29:16  InnoDB: Error: page 7 log sequence number 0 4162857
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 2 log sequence number 0 4329329
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 4 log sequence number 0 4306025
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 11 log sequence number 0 4033091
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 310 log sequence number 0 4033091
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 5 log sequence number 0 4331210
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 6 log sequence number 0 4325621
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 45 log sequence number 0 4325621
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 207 log sequence number 0 4331200
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 1 log sequence number 0 4329081
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 0 log sequence number 0 4329329
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 8 log sequence number 0 4164765
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 10 log sequence number 0 4131615
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 9 log sequence number 0 4164760
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Error: page 12 log sequence number 0 4056397
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
InnoDB: Last MySQL binlog file position 0 21257, file name .\ERDEM-bin.152
050414 13:29:16  InnoDB: Flushing modified pages from the buffer pool...
050414 13:29:16  InnoDB: Error: page 565 log sequence number 0 4056397
InnoDB: is in the future! Current system log sequence number 0 3237920.
InnoDB: Your database may be corrupt.
050414 13:29:16  InnoDB: Started
InnoDB: !!! innodb_force_recovery is set to 4 !!!
mysqld-nt: ready for connections.
Version: '4.0.20a-nt'  socket: ''  port: 3306

InnoDB: !!! innodb_force_recovery is set to 4 !!!
mysqld-nt: ready for connections.
Version: '4.0.20a-nt'  socket: ''  port: 3306
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.

050414 13:30:56  InnoDB: Error: page 384 log sequence number 0 3690645
InnoDB: is in the future! Current system log sequence number 0 3237930.
InnoDB: Your database may be corrupt.
050414 13:30:56  InnoDB: Error: page 385 log sequence number 0 4326555
InnoDB: is in the future! Current system log sequence number 0 3237930.
InnoDB: Your database may be corrupt.
050414 13:30:56  InnoDB: Error: page 405 log sequence number 0 4329329
InnoDB: is in the future! Current system log sequence number 0 3237930.
InnoDB: Your database may be corrupt.
050414 13:30:56  InnoDB: Error: page 411 log sequence number 0 4164755
InnoDB: is in the future! Current system log sequence number 0 3237930.
InnoDB: Your database may be corrupt.
Error: rec is NULL pointer
050414 13:30:56InnoDB: Assertion failure in thread 580 in file C:\cygwin\home\my
sqldev\build\build_gpl-20040527\mysql-4.0.20a\innobase\rem\rem0rec.c line 116
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. See section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about forcing recovery.

How to repeat:
mysqld-nt --innodb_force_recovery=4 --console

Suggested fix:
mysqld-nt --innodb_force_recovery=4 --console

We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.