linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shane Shrybman <shrybman@sympatico.ca>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2-mm3 and mysql
Date: 03 Aug 2003 11:01:52 -0400	[thread overview]
Message-ID: <1059922912.2282.15.camel@mars.goatskin.org> (raw)
In-Reply-To: <20030802190859.3384ee08.akpm@osdl.org>

On Sat, 2003-08-02 at 22:08, Andrew Morton wrote:
> Shane Shrybman <shrybman@sympatico.ca> wrote:
> >
> > The db corruption hit again on test2-mm2.
> 
> How do you know it is "db corruption"?

I haven't been able to get an exact recipe for producing this but I have
posted a couple of the mysql corruption messages.

I still haven't been able to make it appear in 2.6.0-test1-mm1, but once
when I rebooted from -test1-mm1 to -test2-mm3 the tables had problems
immediately, when they came up clean in -test1-mm1 right before. When I
ran the mysql repair tables command it fixed them up and did not delete
any rows from the corrupted table, (or only very few). The repair
command usually deletes thousands of rows in order to repair the table.

http://zeke.yi.org/linux/mysql.tables.corrupt

I haven't found any info on this error message but maybe someone has
seen it before?

BTW: I am using myisam table type in mysql.

I will let you know if I find the exact way to reproduce this problem.

Regards,

Shane


  reply	other threads:[~2003-08-03 15:01 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 [this message]
2003-08-03 19:25         ` Andrew Morton
2003-08-03 18:58   ` Sergey S. Kostyliov
2003-08-04  0:05     ` Matt Mackall
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=1059922912.2282.15.camel@mars.goatskin.org \
    --to=shrybman@sympatico.ca \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).