Sergey, I replied to the Linux kernel mailing list 10 min ago :). Below my reply.
Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ............. Sergey, does it always crash when you start mysqld? It is page number 0 in the InnoDB tablespace. That is, the header page of the whole tablespace! The checksums in the page are ok. That shows the page was not corrupted in the Linux file system. InnoDB is trying to do an index search, but that of course crashes, because the header page is not any index page. The reason for the crash is probably that a page number in a pointer record in the father node of the B-tree has been reset to zero. The corruption has happened in the mysqld process memory, not in the file system of Linux. Otherwise, InnoDB would have complained about page checksum errors. No one else has reported this error. I have now added a check to a future version of InnoDB which will catch this particular error earlier and will hex dump the father page. By the way, I noticed that a website http://www.linuxtestproject.org has made an extensive regression test suite for Linux. They have also successfully run big MySQL and DB2 stress tests on their computers, on 2.5.xx kernels. If there is something wrong with 2.5.xx or 2.6.0, it apparently does not concern all computers. " The Linux Test Project test suite, ltp-20030807, has been released. The latest version of the testsuite contains 2000+ tests for the Linux OS. " The general picture about InnoDB corruption is that reports have almost stopped after I advised people on the mailing list to upgrade to Linux-2.4.20 kernels. With apologies, Heikki Innobase Oy http://www.innodb.com " 030827 15:34:10 InnoDB: Page checksum 1165918361, prior-to-4.0.14-form checksum 4088416325 InnoDB: stored checksum 1165918361, prior-to-4.0.14-form stored checksum 4088416325 InnoDB: Page lsn 0 4080819655, low 4 bytes of lsn at page end 4080819655 InnoDB: Page directory corruption: supremum not pointed to 030827 15:34:10 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex 457e8099000000000000000000000000000000 00f33c5dc7000000000000f356ce970000000100000000000000 0000040f0000040240000000000000006c00000002000400000 1b60004000001de0000000400028000144e00040000009e0000 00360000000001160002800015de0000000000000b410000000 20000000200260002b5e500260000000200027d300026000119 3a0026000000000000000000014000207e00018000009e00000 003aaaaaaaaaaaaaaaa ... 000000000000000f3b04845f33c5dc7 " ..................... Subject: Fwd: 2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql) From: Sergey S. Kostyliov Date: Thu, 28 Aug 2003 21:50:02 +0400 Hello all, This is the copy of my post to linux-kernel list over a hour ago. Am I the only one having problems with 2.6.0-testX linux kernels and InnoDB? ---------- Forwarded Message ---------- Subject: 2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql) Date: Thursday 28 August 2003 20:15 From: "Sergey S. Kostyliov" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hello all, On Wednesday 27 August 2003 19:52, Sergey S. Kostyliov wrote: > On Monday 04 August 2003 04:05, Matt Mackall wrote: <cut> > > All Linux kernels prior to 2.6.0-test2-mm3-1 would silently fail to > > complete fsync() and msync() operations if they encountered an I/O > > error, resulting in corruption. If a particular disk subsystem was > > producing these errors, the symptoms would likely be: > > > > - no error reported > > - no messages in logs > > - independent of kernel version, etc. > > - suddenly appear at some point in drive life > > - works flawlessly on other machines > > > > If you can reproduce this corruption, please try running against mm3-1 > > and seeing if it reports problems (both to fsync and in logs). > > I've just got another one InnoDB crash with 2.6.0-test4. > As in previous case there was no messages in kernel log. > You can find mysql error log here. > Re: 2.6.0-test2-mm3 and mysql And here is another one InnoDB crash I've just got with 2.6.0-test4. http://sysadminday.org.ru/linux-2.6.0-test4_InnoDB_crash-20030828 No messages in kernel log :(( > It's a development server, so this isn't a big problem. > I do understand that this can easily be a hardware problem, > but the kernel silence is really sad in such case. > Memory is fine (at least according to memtest 3.0). > > Any hints will be appreciated. -- Best regards, Sergey S. Kostyliov <[EMAIL PROTECTED]> Public PGP key: http://sysadminday.org.ru/rathamahata.asc -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
