Ravi,
please open a bug report at http://bugs.mysql.com and attach the COMPLETE
UNEDITED .err log to that bug report.
Looks like InnoDB accesses a page filled with zeros. This might be a
hardware fault or an OS bug, as well as an InnoDB bug.
Best regards,
Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
----- Original Message -----
From: "Ravi Prasad LR" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, January 11, 2006 2:13 PM
Subject: Mysql Server crashes saying Page directory corruption
Hi all,
Server version :4.0.26
OS: FeeBSD-4.10
The mysql server(slave) crashes with the following messages in its error
log, and gets restarted, after which rollbacks and starts replicating from
master
Page directory corruption: supremum not pointed to
051226 10:02:58 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
0000000000000000000000000000000000000000000000000000.....(many
0's)
;InnoDB: End of page dump
051226 10:02:58 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form
checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Error: trying to access a stray pointer 0xc9c1bff8
InnoDB: buf pool start is at 0x52a4000, number of pages 70400
051226 10:02:58InnoDB: Assertion failure in thread 20491 in
file ../../innobase/page/../include/buf0buf.ic line 286
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/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
mysqld got signal 11;
it is a slave server replicating from a master. There are no reads
happening
while server crashed. This has happened couple of times. we tried
restoring
mysql with a backup of master. But it goes through fine for few days(2-3
days) , after which the same error reiterated.
what does this error mean?
Please help me in figuring out this error.
Thanks ,
Ravi
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
