Messages in this thread | | | Date | Sun, 3 Aug 2003 11:55:22 -0500 | From | Matt Mackall <> | 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.
-- Matt Mackall : http://www.selenic.com : of or relating to the moon - 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/
| |