Innodb crash under win2000

Innodb crash under win2000

am 09.09.2003 13:29:07 von rafarife

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 There wasn´t the mysqld-max-nt
service (this service is manual) So, we ran the service. Then, I
tried to check the database but I lost the connection when I was
checking a determined table, lincompras. So I run the service again,
and altered the lincompras table type to myisam and later to innodb,
checked again the database and didn´t get any error. The error log file
is:

InnoDB: Dump of the child page:
030909 8:43:03 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 6068cb630000041d00000425000004210000000086968aac45 ....




We have been working without problems but when I have opened the error
log file I have seen the next error:


MySql: preparado para conexiones
030909 12:05:22 InnoDB: error clustered record for sec rec not found
InnoDB: index CliFecArt table peco/linventas
InnoDB: sec index record RECORD: info bits 0 0: len 6; hex 303030333839;
asc 000389;; 1: len 3; hex 8fa6ac; asc .¦¬;; 2: len 8; hex 3030343231343130;
asc 00421410;; 3: len 10; hex 4a41303330b032323137; asc JA030°2217;; 4: len 10;
hex 58413033303033353134; asc XA03003514;; 5: len 2; hex 8001; asc €.;;
InnoDB: clust index record RECORD: info bits 0 0: len 10; hex 4a413033303035313931;
asc JA03005191;; 1: len 0; hex ; asc ;; 2: len 2; hex 8001; asc €.;; 3: len 6;
hex 0000005acd6e; asc ...ZÍn;; 4: len 7; hex 8000005c010084; asc €..\..„;; 5: len 0;
hex ; asc ;; 6: len 3; hex 8fa729; asc .§);; 7: len 2; hex 3030; asc 00;; 8: len 8;
hex 3030323731303430; asc 00271040;; 9: len 32;
hex 524f4c4c4f203530204d54532e43494e5441205445534142414e442d3436 3631;
asc ROLLO 50 MTS.CINTA TESABAND-4661;; 10: len 8; hex 000000000000f03f;
asc ......ð?;; 11: len 1; hex 31; asc 1;; 12: len 8; hex 0000000000004a40; asc ......J@;;
13: len 4; hex 00005242; asc ..RB;; 14: len 8; hex fca9f1d24d023640; asc ü©ñÒM.6@;; 15:
len 4; hex 00008041; asc ..€A;; 16: len 4; hex 00000000; asc ....;; 17: len 2; hex 4547;
asc EG;; 18: len 3; hex 202020; asc ;; 19: len 4; hex 00000000; asc ....;; 20:
TRANSACTION 0 5953488, ACTIVE 1 sec, OS thread id 1864 fetching rows, thread declared
inside InnoDB 415
MySQL thread id 89, query id 54296 192.168.1.210 lourdes Sending data
SELECT `LinVentas`.`Can`, `LinVentas`.`MCa`, `LinVentas`.`Pre`, `LinVentas`.`Dto`,
`Clientes`.`Ruta_Comercial`, `Ruta_Comercial`.`Nom`, `LinVentas`.`C

InnoDB: Make a detailed bug report and send it
InnoDB: to mysql@lists.mysql.com



Any ideas?

Thanks in advance,
Rafa

How-To-Repeat:
-

Fix:
-

Synopsis:Innodb crash under win2000

Submitter-Id:
Originator: Rafa
Organization: Pecomark
MySQL support: none
Severity: critical
Priority: medium
Category: mysqld-max-nt
Class: sw-bug
Release: mysqld 4.0.14

Exectutable: mysqld-max-nt
Environment: 2 Pentium III-MMX, 500 MHZ, 780 MB
System: Windows 2000
Compiler: -
Architecture: i


____________________________________________________________ ______
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?p romo=393397

Get AOL Instant Messenger 5.1 free of charge. Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Innodb crash under win2000

am 09.09.2003 14:49:51 von Sinisa Milivojevic

rafarife@netscape.net writes:
> Description:
> Hello,
> =20
> We are working with mysqld-max-nt 4.0.14 under Win2000 service-pack=
4.
> We have a server with two Pentium-III MMX 500Mhz proccesors and 780=
MB Ram.
> We work with InnoDB tables. We have reserved 300MB to InnoDB and us=
e
> a RAID 5.
>=20
> We were working when Mysql/Innodb crashed. We were not able to=20
> connect to MySql. We noticed that There wasn´t the mysqld-max-=
nt
> service (this service is manual) So, we ran the service. Then, I
> tried to check the database but I lost the connection when I was
> checking a determined table, lincompras. So I run the service again=
,
> and altered the lincompras table type to myisam and later to innodb=
,
> checked again the database and didn´t get any error. The error=
log file
> is:
>=20
Hi!

This list is dedicated to repeatable test cases.

We do not know how to repeat a crash that you are reporting.

It looks like either memory or disk corruption.

But to diagnose better we would need InnoDB checksum report, which you
omitted from the dump.

--=20

Sincerely,

--=20
For technical support contracts, go to https://order.mysql.com/?ref=3Dm=
smi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic >
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB
/_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinat=
or
<___/ www.mysql.com Larnaca, Cyprus


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=3Dgcdmb-bugs@m.gmane.org