Re: kupdate weirdness

2007-08-02 Thread Miklos Szeredi
> There were heaps of problems in there and it is surprising how few people > were hitting them. Ordered-mode journalling filesystems will fix it all up > behind the scenes, of course. > > I just have a bad feeling about that code - list_heads are the wrong data > structure and it all needs to be

Re: kupdate weirdness

2007-08-02 Thread Andrew Morton
On Thu, 02 Aug 2007 17:52:39 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote: > > > The following strange behavior can be observed: > > > > > > 1. large file is written > > > 2. after 30 seconds, nr_dirty goes down by 1024 > > > 3. then for some time (< 30 sec) nothing happens (disk idle) > > > 4.

Re: kupdate weirdness

2007-08-02 Thread Miklos Szeredi
> > The following strange behavior can be observed: > > > > 1. large file is written > > 2. after 30 seconds, nr_dirty goes down by 1024 > > 3. then for some time (< 30 sec) nothing happens (disk idle) > > 4. then nr_dirty again goes down by 1024 > > 5. repeat from 3. until whole file is written >

Re: kupdate weirdness

2007-08-01 Thread David Chinner
On Wed, Aug 01, 2007 at 10:45:16PM +0200, Miklos Szeredi wrote: > The following strange behavior can be observed: > > 1. large file is written > 2. after 30 seconds, nr_dirty goes down by 1024 > 3. then for some time (< 30 sec) nothing happens (disk idle) > 4. then nr_dirty again goes down by 1024

Re: kupdate weirdness

2007-08-01 Thread Andrew Morton
On Wed, 01 Aug 2007 22:45:16 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote: > The following strange behavior can be observed: > > 1. large file is written > 2. after 30 seconds, nr_dirty goes down by 1024 > 3. then for some time (< 30 sec) nothing happens (disk idle) > 4. then nr_dirty again goe

kupdate weirdness

2007-08-01 Thread Miklos Szeredi
The following strange behavior can be observed: 1. large file is written 2. after 30 seconds, nr_dirty goes down by 1024 3. then for some time (< 30 sec) nothing happens (disk idle) 4. then nr_dirty again goes down by 1024 5. repeat from 3. until whole file is written So basically a 4Mbyte chunk