[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090526164117.GJ11363@kernel.dk>
Date: Tue, 26 May 2009 18:41:17 +0200
From: Jens Axboe <jens.axboe@...cle.com>
To: Damien Wyart <damien.wyart@...e.fr>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
chris.mason@...cle.com, david@...morbit.com, hch@...radead.org,
akpm@...ux-foundation.org, jack@...e.cz,
yanmin_zhang@...ux.intel.com, richard@....demon.co.uk
Subject: Re: [PATCH 0/12] Per-bdi writeback flusher threads v7
On Tue, May 26 2009, Damien Wyart wrote:
> Hello,
>
> I have been playing with v7 since your sending and after a white (short
> on laptop, longer on desktop, a few hours), writeback doesn't seem to
> work anymore. Manual call to sync hangs (process in D state) and Dirty
> value in meminfo gets growing. As previous versions had been heavily
> tested, I guess there is some regression in v7.
Not good, the prime suspect is the sync notification stuff. I'll take a
look and get that fixed. You didn't happen to catch any sysrq-t back
traces or anything like that? Would be interesting to see where where
bdi-default and the bdi-* threads are stuck.
Can you send me your .config and a dmesg from a booted system? Any
kernel, doesn't have to be the writeback kernel.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists