Re: [PATCH] Prevent large file writeback starvation

[Andrew Morton]

Mark Lord <lkml@xxxxxx> wrote:
>
> A simple test I do for this:
> 
>  $ mkdir t
>  $ cp /usr/src/*.bz2  t    (about 400-500MB worth of kernel tar files)
> 
>  In another window, I do this:
> 
>  $ while (sleep 1); do echo -n "`date`: "; grep Dirty /proc/meminfo; done
> 
>  And then watch the count get large, but take virtually forever
>  to count back down to a "safe" value.
> 
>  Typing "sync" causes all the Dirty pages to immediately be flushed to disk,
>  as expected.

I've never seen that happen and I don't recall seeing any other reports of
it, so your machine must be doing something peculiar.  I think it can
happen if, say, an inode gets itself onto the wrong inode list, or
incorrectly gets its dirty flag cleared.

Are you using any unusual mount options, or unusual combinations of
filesystems, or anything like that?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/