From: Alexander Bergolth <leo@strike.wu-wien.ac.at>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Mark Lord <lkml@rtr.ca>,
dgc@sgi.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation)
Date: Tue, 11 Apr 2006 14:42:06 +0200 [thread overview]
Message-ID: <443BA41E.2020403@strike.wu-wien.ac.at> (raw)
In-Reply-To: <20060213135925.GA6173@linuxtv.org>
On 02/13/2006 02:59 PM, Johannes Stezenbach wrote:
> On Mon, Feb 06, 2006, Andrew Morton wrote:
>>Mark Lord <lkml@rtr.ca> wrote:
>>
>>>A simple test I do for this:
>>>
>>> $ mkdir t
>>> $ cp /usr/src/*.bz2 t (about 400-500MB worth of kernel tar files)
>>>
>>> In another window, I do this:
>>>
>>> $ while (sleep 1); do echo -n "`date`: "; grep Dirty /proc/meminfo; done
>>>
>>> And then watch the count get large, but take virtually forever
>>> to count back down to a "safe" value.
>>>
>>> Typing "sync" causes all the Dirty pages to immediately be flushed to disk,
>>> as expected.
>>
>>I've never seen that happen and I don't recall seeing any other reports of
>>it, so your machine must be doing something peculiar. I think it can
>>happen if, say, an inode gets itself onto the wrong inode list, or
>>incorrectly gets its dirty flag cleared.
Are you still suffering from this problem?
I'm seeing exactly the same issue on many boxes (including
kernel-2.6.16). (See my tests and the corresponding test-script at [1].)
Are you using Software-Suspend? I am able to trigger the problem after
suspending to disk and resuming (swsuspend2). However, it does also
happen on some boxes with a stock fedora kernel and without suspending,
though it is hard to reproduce on those boxes. (But once it is
triggered, it doesn't go away anymore.)
On most machines that show the problem, buffers are flushed only based
on the amount of dirty memory (dirty_ratio and dirty_background_ratio)
or when doing a "sync", they are not periodically flushed anymore.
There is one box where even "sync" does only flush a fraction of the
dirty buffers [2].
I am not using vmware, no laptop_mode and no custom /proc/sys/vm/dirty*
settings are involved.
Cheers,
--leo
[1] Tests results and test-script:
http://leo.kloburg.at/tmp/dirty-buffers/
[2] sync does flush only a fraction of dirty buffers:
http://leo.kloburg.at/tmp/dirty-buffers/bad_slime-2.6.14-1.1653_FC4smp.txt
next prev parent reply other threads:[~2006-04-11 12:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 4:00 [PATCH] Prevent large file writeback starvation David Chinner
2006-02-06 4:27 ` Andrew Morton
2006-02-06 5:48 ` David Chinner
2006-02-06 6:22 ` Andrew Morton
2006-02-06 6:36 ` Andrew Morton
2006-02-06 11:57 ` David Chinner
2006-02-06 11:55 ` David Chinner
2006-02-06 23:14 ` Andrew Morton
2006-02-07 0:34 ` David Chinner
2006-02-07 1:04 ` Andrew Morton
2006-02-07 1:31 ` David Chinner
2006-02-07 5:27 ` Andrew Morton
2006-02-07 7:42 ` David Chinner
2006-02-07 22:51 ` Andrew Morton
2006-02-07 7:49 ` David Chinner
2006-02-06 14:36 ` Mark Lord
2006-02-06 14:39 ` Mark Lord
2006-02-06 20:11 ` Andrew Morton
2006-02-13 13:59 ` dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation) Johannes Stezenbach
2006-02-13 20:08 ` Andrew Morton
2006-02-13 22:48 ` Johannes Stezenbach
2006-02-13 23:04 ` Andrew Morton
2006-02-13 23:31 ` Johannes Stezenbach
2006-02-13 23:52 ` Mark Lord
2006-02-14 0:50 ` Mark Lord
2006-02-14 16:32 ` Mark Lord
2006-04-11 12:42 ` Alexander Bergolth [this message]
2006-03-20 22:40 ` [PATCH] Prevent large file writeback starvation Alexander Bergolth
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=443BA41E.2020403@strike.wu-wien.ac.at \
--to=leo@strike.wu-wien.ac.at \
--cc=dgc@sgi.com \
--cc=js@linuxtv.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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).