From: Greg Smith <gsmith@gregsmith.com>
To: M. Edward (Ed) Borasky <zznmeb@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: "iowait" bug?
Date: Sun, 22 Mar 2009 16:17:40 -0400 (EDT)
Message-ID: <alpine.GSO.2.01.0903221507500.8979@westnet.com> (raw)
In-Reply-To: <af0420cd0903202117i66109820s31b440bc7648c358@mail.gmail.com>
References: <af0420cd0903200945m7f70d057p12942b50c8266bcb@mail.gmail.com>
<af0420cd0903202117i66109820s31b440bc7648c358@mail.gmail.com>
On Fri, 20 Mar 2009, M. Edward (Ed) Borasky wrote:
> I just discovered this on a LinkedIn user group:
> http://bugzilla.kernel.org/show_bug.cgi?id=12309
I would bet there's at least 3 different bugs in that one. That bug
report got a lot of press via Slashdot a few months ago, and it's picked
all sort of people who all have I/O wait issues, but they don't all have
the same cause. The 3ware-specific problem Laurent mentioned is an
example. That's not the same thing most of the people there are running
into, the typical reporter there has disks attached directly to their
motherboard. The irony here is that #12309 was a fork of #7372 to start
over with a clean discussion slat because the same thing happened to that
earlier one.
The original problem reported there showed up in 2.6.20, so I've been able
to avoid this whole thing by sticking to the stock RHEL5 kernel (2.6.18)
on most of the production systems I deal with. (Except for my system with
an Areca card--that one needs 2.6.22 or later to be stable, and seems to
have no unexpected I/O wait issues. I think this is because it's taking
over the lowest level I/O scheduling from Linux, when it pushes from the
card's cache onto the disks).
Some of the people there reported significant improvement by tuning the
pdflush tunables; now that I've had to do a few times on systems to get
rid of unexpected write lulls. I wrote up a walkthrough on one of them at
http://notemagnet.blogspot.com/2008/08/linux-write-cache-mystery.html that
goes over how to tell if you're running into that problem, and what to do
about it; something else I wrote on that already made it into the bug
report in comment #150.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com, zznmeb@gmail.com
Subject: Re: "iowait" bug?
In-Reply-To: <alpine.GSO.2.01.0903221507500.8979@westnet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox