Andrew,
a possible reason for the corruption is that you have enabled write caching
in the disk controller or in the disk, but those caches are not
battery-backed. Then a hard reboot may destroy the contents, and the
database becomes corrupt.
What kind of hardware are you using? Do you have manuals that would describe
the write caching policy?
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: ""Andrew Brockert"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Sunday, May 21, 2006 4:59 AM
Subject: InnoDB corruption and crash on Windows 2000
------=_Part_127305_14374727.1148176365800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
I am running MySQL with hMailServer on Windows 2000 Pro. I was forced to
hard reboot the machine this morning, and this is now the result of
running
mysqld-nt with --console:
060520 21:38:23 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 4648603
InnoDB: Doing recovery: scanned up to log sequence number 0 4648603
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 478464
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Cleaning up trx with id 0 406541
InnoDB: Rollback of uncommitted transactions completed
060520 21:38:23 InnoDB: Flushing modified pages from the buffer pool...
060520 21:38:23 InnoDB: Started
N:\hMailServer\MySQL\Bin\mysqld-nt.exe: ready for connections.
Version: '4.0.17-nt' socket: '' port: 3307
060520 21:38:24 InnoDB: Error: page 209 log sequence number 0 4672346
InnoDB: is in the future! Current system log sequence number 0 4648603.
InnoDB: Your database may be corrupt.
060520 21:38:24 InnoDB: Assertion failure in thread 2328 in file
C:\4017\build\mysql-4.0.17\innobase\fsp\fsp0fsp.c line 3034
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
InnoDB: Thread 2732 stopped in file C:\4017\build\mysql-
4.0.17\innobase\sync\sync0arr.c line 126
------=_Part_127305_14374727.1148176365800--
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
