From: "Heikki Tuuri" <Heikki.Tuuri@innodb.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2-mm3 and mysql
Date: Sun, 3 Aug 2003 20:11:29 +0300 [thread overview]
Message-ID: <004c01c359e2$47db2110$322bde50@koticompaq> (raw)
In-Reply-To: 20030803165522.GS22824@waste.org
Matt,
----- Original Message -----
From: "Matt Mackall" <mpm@selenic.com>
To: "Heikki Tuuri" <Heikki.Tuuri@innodb.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, August 03, 2003 7:55 PM
Subject: Re: 2.6.0-test2-mm3 and mysql
> On Sun, Aug 03, 2003 at 12:10:01PM +0300, Heikki Tuuri wrote:
> >
> > What to do? People who write drivers should run heavy, multithreaded
file
> > i/o tests on their computer using some SQL database which calls fsync().
For
> > example, run the Perl '/sql-bench/innotest's all concurrently on MySQL.
If
> > the problems are in drivers, that could help.
>
> Did you know that until test2-mm3, nothing would report errors that
> occurred on non-synchronous writes? There was no infrastructure to
> propagate the error back to userspace. If you wrote a page, the write
> failed on an intermittent I/O error, and then read again, you'd
> silently get back the old page.
we are not using the Linux async i/o. Do you mean that? Or the flush which
the Linux kernel does from the file cache to the disk time to time on its
own? I assume it will write to the system log an error message if a disk
write fails?
The error 5 Shane reported came from a call of fsync(), and apparently he
also got that same 5 from a simple file read which CHECK TABLE in MyISAM
does.
Why would a write in the Linux async i/o fail? I am using aio on Windows,
and if the disk space can be allocated, it seems to fail only in the case of
a hardware failure.
> --
> Matt Mackall : http://www.selenic.com : of or relating to the moon
Regards,
Heikki
next prev parent reply other threads:[~2003-08-03 17:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-08-03 23:54 ` Matt Mackall
-- strict thread matches above, loose matches on Subject: below --
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
2003-08-03 20:50 Heikki Tuuri
2003-08-03 16:59 Heikki Tuuri
2003-08-03 23:57 ` Matt Mackall
2003-08-03 0:38 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
2003-08-27 15:52 ` 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='004c01c359e2$47db2110$322bde50@koticompaq' \
--to=heikki.tuuri@innodb.com \
--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).