On Thu, May 20, 2010 at 06:11:21PM +0200, Jan Kara wrote:
quoted text
>   Hmm, I'm not seeing anything obviously wrong with that patch but
> apparently the number of blocks reserved for delayed allocation is
> miscomputed by a lot...

IIRC this only affects NFS clients.  The same test running locally on
the server doesn't show the same problem.  I will retest shortly and
confirm (and also test with 2.6.34).

quoted text
>   Is your ext4 filesystem create from scratch or converted from ext3?

I converted from ext3.

quoted text
>   Is
> your application using lots of different files or rather a couple of small
> ones?

The application writes over NFS two files using writev.  One is
currently about 38MB and the other is under 1MB.

The "application" FWIW is saving games over NFS from Wesnoth.  At least
that's the most obvious application I have found that can reliably
trigger the problem.  I did notice the problem at several times when the
game was not even running, but couldn't pin down what else was
happening.

quoted text
> Anyways a reproducing program would be the best in this case...

I will try to code something up to reproduce the symptoms using the
system call trace as a reference.

-- 
Bruce Guenter <bruce@untroubled.org>                http://untroubled.org/