lkml.org 
[lkml]   [2003]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: 2.6.0-test2-mm3 and mysql
    Date
    On Monday 04 August 2003 04:05, Matt Mackall wrote:
    > On Sun, Aug 03, 2003 at 10:58:17PM +0400, Sergey S. Kostyliov wrote:
    > > Hello Andrew,
    > >
    > > On Sunday 03 August 2003 05:04, Andrew Morton wrote:
    > > > Shane Shrybman <shrybman@sympatico.ca> wrote:
    > > > > One last thing, I have started seeing mysql database corruption
    > > > > recently. I am not sure it is a kernel problem. And I don't know the
    > > > > exact steps to reproduce it, but I think I started seeing it with
    > > > > -test2-mm2. I haven't ever seen db corruption in the 8-12 months I
    > > > > have being playing with mysql/php.
    > > >
    > > > hm, that's a worry. No additional info available?
    > >
    > > I also suffer from this problem (I'm speaking about heavy InnoDB
    > > corruption here), but with vanilla 2.6.0-test2. I can't blame
    > > MySQL/InnoDB because there are a lot of MySQL boxes around of me with the
    > > same (in fact the box wich failed is replication slave) or allmost the
    > > same database setup. All other boxes (2.4 kernel) works fine up to now.
    >
    > 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.
    http://sysadminday.org.ru/linux-2.6.0-test4_InnoDB_crash

    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 <rathamahata@php4.ru>
    Public PGP key: http://sysadminday.org.ru/rathamahata.asc
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

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