[lkml]   [2003]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql)
Hello all,

On Wednesday 27 August 2003 19:52, Sergey S. Kostyliov wrote:
> On Monday 04 August 2003 04:05, Matt Mackall wrote:


> > 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.
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 <>
Public PGP key:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:48    [W:0.079 / U:0.872 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site