3 messages in com.mysql.lists.bugsRe: MySQL/Innodb crash under Win2000| From | Sent On | Attachments |
|---|---|---|
| rafa...@netscape.net | 02 Sep 2003 04:06 | |
| Sinisa Milivojevic | 02 Sep 2003 04:19 | |
| Heikki Tuuri | 04 Sep 2003 00:37 |
| Subject: | Re: MySQL/Innodb crash under Win2000![]() |
|---|---|
| From: | Sinisa Milivojevic (sin...@mysql.com) |
| Date: | 09/02/2003 04:19:40 AM |
| List: | com.mysql.lists.bugs |
rafa...@netscape.net writes:
Description: Hello,
We are working with mysqld-max-nt 4.0.14 under Win2000 service-pack4. We have a server with two Pentium-III MMX 500Mhz proccesors and 780MB Ram. We work with InnoDB tables. We have reserved 300MB to InnoDB and use a RAID 5.
We were working when Mysql/Innodb crashed. We were not able to connect to MySql. We noticed that the mysqld-max-nt service was stopped (this service is manual). So, we run the service and We continue working without problems.
The Error log file is:
MySql: ready for connections InnoDB: Next record offset nonsensical 34764 for rec 1965 030902 12:32:10 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex 06f38e7500004.......
Any ideas?
Thanks in advance, Rafa
How-To-Repeat: -
Fix: -
HI!
This looks like disc / memory corruption.
It happnes usually on faulty hardware or on OS with buggy device drivers.
--
Sincerely,
-- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sin...@mysql.com> / /|_/ / // /\ \/ /_/ / /__ MySQL AB /_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator <___/ www.mysql.com Larnaca, Cyprus




