Shane,
"
| tv01.program | check | error | got error: 5 when reading datafile
at record: 6696 |
"
InnoDB reported that same error 5 "EIO I/O error" in a call of fsync().
MyISAM never calls fsync(), but I guess these problems are related. Let us
hope Andrew's fix fixes this MyISAM problem, too.
Before your case I have not seen MyISAM report table corruption with error
5. A brief Googling only returns 4 reports of 'got error: 5'. Thus, it is
likely that the bug in this case is in the OS/drivers/hardware.
Regards,
Heikki
....................
List: linux-kernel
Subject: Re: 2.6.0-test2-mm3 and mysql
From: Shane Shrybman <shrybman () sympatico ! ca>
Date: 2003-08-03 15:01:52
[Download message RAW]
On Sat, 2003-08-02 at 22:08, Andrew Morton wrote:
> Shane Shrybman <[email protected]> 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
On Sun, Aug 03, 2003 at 07:59:37PM +0300, Heikki Tuuri wrote:
> Shane,
>
> "
> | tv01.program | check | error | got error: 5 when reading datafile
> at record: 6696 |
> "
>
> InnoDB reported that same error 5 "EIO I/O error" in a call of fsync().
> MyISAM never calls fsync(), but I guess these problems are related. Let us
> hope Andrew's fix fixes this MyISAM problem, too.
Andrew introduced a buglet to my sync fixes -mm3 that reported IO
errors on any sync(). The logic in -mm3-1 should fix this and actually
report failed syncs.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon