On Tue, Oct 30, 2007 at 07:49:41PM +0800, Fengguang Wu wrote:
quoted text
> On Tue, Oct 30, 2007 at 06:42:50AM -0500, Florin Iucha wrote:
> > On Tue, Oct 30, 2007 at 03:54:03PM +0800, Fengguang Wu wrote:
> > > It could be triggered by the more aggressive writeback behavior - the
> > > new code will keep on retrying as long as there are dirty inodes pend=
ing.
quoted text
> > >=20
> > > Florin, would you try the attached patches against 2.6.24-git?
> > > They may generate big traffic of printk messages, but will help
> > > debug the problem.
> >=20
> > I have updated to v2.6.24-rc1-334-g82798a1.  After using my computer
> > for two hours, I left the computer idle overnight.  This morning,
> > pdflushd is again consuming 25% of a CPU.  I will try Fengguang's
> > patches today.
>=20
> Thank you.
>=20
> Be sure to stop klogd ;-)
> A `dmesg` will be sufficient for debugging.
>=20
> btw, I cannot reproduce it with simple NFSv3 tests.

This is using nfsv4.  And being idle in a GNOME session with home
mounted from the server is hardly a stressful experience.  But what do
I know ;)

florin

--=20
Bruce Schneier expects the Spanish Inquisition.
      http://geekz.co.uk/schneierfacts/fact/163