public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
Date: Thu, 1 Nov 2007 21:03:33 +0800	[thread overview]
Message-ID: <393922219.19211@ustc.edu.cn> (raw)
Message-ID: <E1InZht-0004lr-NN@localhost> (raw)
In-Reply-To: <20071101122558.GX25561@iucha.net>

On Thu, Nov 01, 2007 at 07:25:58AM -0500, Florin Iucha wrote:
> On Thu, Nov 01, 2007 at 03:15:32PM +0800, Fengguang Wu wrote:
> > On Wed, Oct 31, 2007 at 12:53:18PM -0500, Florin Iucha wrote:
> > > This patch does not fix anything for me.  Even such light use of the
> > > reiserfs filesystem as pulling the linux-2.6 git tree updates caused
> > > one CPU to go to 75% iowait.
> >  
> > Thank you, Florin. Could you provide more details about sda7, such as
> > the mount option and output of `reiserfstune /dev/sda7`? I'll try to
> > reproduce it before asking for your help.
> 
> Fengguang,
> 
> root@zeus:~# mount | grep sda7
> /dev/sda7 on /scratch type reiserfs (rw,noatime)
> root@zeus:~# df -h /scratch/
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda7              38G   32G  5.7G  85% /scratch
[...]

Thank you. It seems the only difference with mine reiserfs is about
the 'noatime' - which I tried and saw no difference.

Or will the system or fs size/age make any difference? If you happen
to have a spare/swap partition, could you make a new reiserfs and
mount it and copy several less-than-4KB files into it and wait for 30s
and see what happen to pdflush?

btw, what's the exact kernel version you are running?

Thank you,
Fengguang


  reply	other threads:[~2007-11-01 13:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 15:24 pdflush stuck in D state with v2.6.24-rc1-192-gef49c32 Florin Iucha
2007-10-29 13:46 ` Trond Myklebust
2007-10-29 15:01   ` Florin Iucha
2007-10-29 18:43     ` Trond Myklebust
2007-10-29 18:48       ` Florin Iucha
     [not found] ` <E1ImlvH-0003YH-Qf@localhost>
2007-10-30  7:54   ` Fengguang Wu
2007-10-30 11:42   ` Florin Iucha
     [not found]     ` <E1ImpbK-0000l3-1u@localhost>
2007-10-30 11:49       ` Fengguang Wu
2007-10-30 11:55       ` Florin Iucha
2007-10-31  0:02       ` Florin Iucha
2007-10-31  3:52         ` Florin Iucha
     [not found]           ` <E1In7S9-0001rv-NO@localhost>
2007-10-31  6:53             ` Fengguang Wu
2007-10-31 12:16             ` Florin Iucha
2007-10-31 17:53               ` Florin Iucha
     [not found]                 ` <E1InUH6-0001vE-1Y@localhost>
2007-11-01  7:15                   ` Fengguang Wu
2007-11-01 12:25                   ` Florin Iucha
     [not found]                     ` <E1InZht-0004lr-NN@localhost>
2007-11-01 13:03                       ` Fengguang Wu [this message]
2007-11-01 14:14                       ` Florin Iucha
     [not found]                         ` <E1InlPV-0001f1-SL@localhost>
2007-11-02  1:33                           ` Fengguang Wu
2007-11-02  2:10                           ` Florin Iucha
     [not found]                             ` <E1Inw51-0001e8-PS@localhost>
2007-11-02 12:56                               ` Fengguang Wu
2007-11-02 13:32                               ` Florin Iucha
2007-11-11 13:43                                 ` Thomas
2007-12-04 10:28                                   ` [Bug 9291] " Ingo Molnar
2007-12-04 17:45                                     ` Thomas Kuther

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=393922219.19211@ustc.edu.cn \
    --to=wfg@mail.ustc.edu.cn \
    --cc=florin@iucha.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=trond.myklebust@fys.uio.no \
    /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