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]
