From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: Chakri n <chakriin5@gmail.com>, Krzysztof Oledzki <olel@ans.pl>,
akpm@linux-foundation.org,
linux-pm <linux-pm@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?)
Date: Sat, 29 Sep 2007 16:43:55 +0200 [thread overview]
Message-ID: <1191077035.18147.118.camel@lappy> (raw)
In-Reply-To: <391068925.28146@ustc.edu.cn>
On Sat, 2007-09-29 at 20:28 +0800, Fengguang Wu wrote:
> On Sat, Sep 29, 2007 at 01:48:01PM +0200, Peter Zijlstra wrote:
> > On the patch itself, not sure if it would have been enough. As soon as
> > there is a single dirty inode on the list one would get caught in the
> > same problem as before.
>
> That should not be a problem. Normally the few new dirty inodes will
> be all cleaned in one go and there are no more dirty inodes left(at
> least for a moment). Hmm, I guess the new 'break' should be moved
> immediately after writeback_inodes()...
>
> > That is, if NFS_dirty+NFS_unstable+NFS_writeback > dirty_limit this
> > break won't fix it.
>
> In fact this patch exactly targets at this condition.
> When NFS* < dirty_limit, Chakri won't see the lockup at all.
> The problem was, there are only two 'break's in the loop, and neither
> one evaluates to true for his dd command.
Yeah indeed, when put in the loop, after writeback_inodes() it makes
sense.
No idea what I was thinking, must be one of those days... :-/
next prev parent reply other threads:[~2007-09-29 14:48 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 6:32 A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?) Chakri n
2007-09-28 6:50 ` Andrew Morton
2007-09-28 6:50 ` Andrew Morton
2007-09-28 6:59 ` Peter Zijlstra
2007-09-28 6:59 ` Peter Zijlstra
2007-09-28 8:27 ` Chakri n
2007-09-28 8:27 ` Chakri n
2007-09-28 8:27 ` Chakri n
2007-09-28 8:40 ` Peter Zijlstra
2007-09-28 9:01 ` Chakri n
2007-09-28 9:01 ` Chakri n
2007-09-28 9:01 ` Chakri n
2007-09-28 9:12 ` Peter Zijlstra
2007-09-28 9:12 ` Peter Zijlstra
2007-09-28 9:20 ` Chakri n
2007-09-28 9:20 ` Chakri n
2007-09-28 9:23 ` Peter Zijlstra
2007-09-28 9:23 ` Peter Zijlstra
2007-09-28 10:36 ` Chakri n
2007-09-28 10:36 ` Chakri n
2007-09-28 10:36 ` Chakri n
2007-09-28 9:23 ` Peter Zijlstra
2007-09-28 9:20 ` Chakri n
2007-09-28 8:40 ` Peter Zijlstra
2007-09-28 13:28 ` Jonathan Corbet
2007-09-28 13:28 ` Jonathan Corbet
2007-09-28 13:28 ` Jonathan Corbet
2007-09-28 13:35 ` Peter Zijlstra
2007-09-28 16:45 ` Alan Stern
2007-09-28 16:45 ` [linux-pm] " Alan Stern
2007-09-28 16:45 ` Alan Stern
2007-09-29 1:27 ` Daniel Phillips
2007-09-29 1:27 ` Daniel Phillips
2007-09-29 1:27 ` Daniel Phillips
2007-09-28 13:35 ` Peter Zijlstra
2007-09-28 18:04 ` Andrew Morton
2007-09-28 18:04 ` Andrew Morton
2007-09-28 18:04 ` Andrew Morton
2007-09-28 17:00 ` Trond Myklebust
2007-09-28 18:49 ` Andrew Morton
2007-09-28 18:49 ` Andrew Morton
2007-09-28 18:48 ` Peter Zijlstra
2007-09-28 18:48 ` Peter Zijlstra
2007-09-28 19:16 ` Andrew Morton
2007-09-28 19:16 ` Andrew Morton
2007-09-28 19:16 ` Andrew Morton
2007-10-02 13:36 ` Peter Zijlstra
2007-10-02 15:42 ` Randy Dunlap
2007-10-03 9:28 ` [PATCH] lockstat: documentation Peter Zijlstra
2007-10-03 9:35 ` Ingo Molnar
2007-09-28 19:16 ` A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?) Trond Myklebust
2007-09-28 19:16 ` Trond Myklebust
2007-09-28 19:26 ` Andrew Morton
2007-09-28 19:26 ` Andrew Morton
2007-09-28 19:26 ` Andrew Morton
2007-09-28 19:52 ` Trond Myklebust
2007-09-28 19:52 ` Trond Myklebust
2007-09-28 20:10 ` Andrew Morton
2007-09-28 20:10 ` Andrew Morton
2007-09-28 20:32 ` Trond Myklebust
2007-09-28 20:32 ` Trond Myklebust
2007-09-28 20:32 ` Trond Myklebust
2007-09-28 20:43 ` Andrew Morton
2007-09-28 20:43 ` Andrew Morton
2007-09-28 21:36 ` Chakri n
2007-09-28 21:36 ` Chakri n
2007-09-28 23:33 ` Chakri n
2007-09-28 23:33 ` Chakri n
2007-09-28 23:33 ` Chakri n
2007-09-28 20:10 ` Andrew Morton
2007-09-28 20:24 ` Daniel Phillips
2007-09-28 20:24 ` Daniel Phillips
2007-09-28 19:52 ` Trond Myklebust
2007-09-29 1:51 ` KDB? Daniel Phillips
2007-09-29 1:51 ` KDB? Daniel Phillips
2007-09-29 1:51 ` KDB? Daniel Phillips
2007-09-28 18:49 ` A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?) Andrew Morton
2007-09-28 17:00 ` Trond Myklebust
2007-09-29 0:46 ` Daniel Phillips
2007-09-29 0:46 ` Daniel Phillips
2007-09-29 0:46 ` Daniel Phillips
2007-09-29 11:04 ` Fengguang Wu
2007-09-29 11:04 ` Fengguang Wu
2007-09-29 11:48 ` Peter Zijlstra
2007-09-29 12:28 ` Fengguang Wu
2007-09-29 12:28 ` Fengguang Wu
2007-09-29 14:43 ` Peter Zijlstra
2007-09-29 14:43 ` Peter Zijlstra [this message]
2007-09-29 12:28 ` Fengguang Wu
2007-09-29 11:48 ` Peter Zijlstra
2007-10-01 15:57 ` Chuck Ebbert
2007-10-02 2:00 ` [PATCH] writeback: avoid possible balance_dirty_pages() lockup on a light-load bdi Fengguang Wu
2007-10-02 2:00 ` Fengguang Wu
2007-10-02 2:00 ` Fengguang Wu
2007-10-02 2:14 ` Andrew Morton
2007-10-02 2:14 ` Andrew Morton
2007-10-02 12:13 ` Fengguang Wu
2007-10-02 12:13 ` Fengguang Wu
2007-10-02 12:13 ` Fengguang Wu
2007-10-02 13:27 ` Fengguang Wu
2007-10-02 13:27 ` Fengguang Wu
2007-10-02 13:27 ` Fengguang Wu
2007-10-02 18:35 ` Chuck Ebbert
2007-10-02 18:35 ` Chuck Ebbert
2007-10-03 12:46 ` richard kennedy
2007-10-04 1:50 ` Fengguang Wu
2007-10-04 1:50 ` Fengguang Wu
2007-10-04 1:50 ` Fengguang Wu
2007-10-03 12:46 ` richard kennedy
2007-10-01 15:57 ` A unresponsive file system can hang all I/O in the system on linux-2.6.23-rc6 (dirty_thresh problem?) Chuck Ebbert
2007-09-29 11:04 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2007-09-28 6:32 Chakri n
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=1191077035.18147.118.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=chakriin5@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=olel@ans.pl \
--cc=wfg@mail.ustc.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.