From: Matt Mackall <mpm@selenic.com>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: Andrew Morton <akpm@osdl.org>,
Shane Shrybman <shrybman@sympatico.ca>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm3 and mysql
Date: Sun, 3 Aug 2003 19:05:14 -0500 [thread overview]
Message-ID: <20030804000514.GY22824@waste.org> (raw)
In-Reply-To: <200308032258.17450.rathamahata@php4.ru>
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).
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-08-04 0:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 0:38 2.6.0-test2-mm3 and mysql Shane Shrybman
2003-08-03 1:04 ` Andrew Morton
2003-08-03 1:52 ` Con Kolivas
2003-08-03 1:59 ` Andrew Morton
2003-08-03 1:58 ` Shane Shrybman
2003-08-03 2:08 ` Andrew Morton
2003-08-03 15:01 ` Shane Shrybman
2003-08-03 19:25 ` Andrew Morton
2003-08-03 18:58 ` Sergey S. Kostyliov
2003-08-04 0:05 ` Matt Mackall [this message]
2003-08-27 15:52 ` Sergey S. Kostyliov
2003-08-28 16:15 ` 2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql) Sergey S. Kostyliov
2003-08-28 19:50 ` Andrew Morton
2003-08-29 8:12 ` Sergey S. Kostyliov
2003-08-31 10:37 ` Sergey S. Kostyliov
2003-08-31 19:06 ` Andrew Morton
2003-08-03 9:10 2.6.0-test2-mm3 and mysql Heikki Tuuri
2003-08-03 9:27 ` Andrew Morton
2003-08-03 10:43 ` Heikki Tuuri
2003-08-04 12:24 ` Denis Vlasenko
2003-08-04 18:29 ` Heikki Tuuri
2003-08-03 16:55 ` Matt Mackall
2003-08-03 17:11 ` Heikki Tuuri
2003-08-03 23:54 ` Matt Mackall
2003-08-03 16:59 Heikki Tuuri
2003-08-03 23:57 ` Matt Mackall
2003-08-03 20:50 Heikki Tuuri
2003-08-28 17:59 Heikki Tuuri
2003-08-28 19:01 ` Sergey S. Kostyliov
2003-08-28 19:10 ` Heikki Tuuri
2003-08-28 19:27 ` Sergey S. Kostyliov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030804000514.GY22824@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@php4.ru \
--cc=shrybman@sympatico.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).