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 of the file is written every 30 seconds. I'm quite sure this is not the intended behavior. The reason seems to be that __sync_single_inode() will move the partially written inode from s_io onto s_dirty, and sync_sb_inode() will not splice it back onto s_io until the rest of the inodes on s_io has been processed. Since there will probably be a recently dirtied inode on s_io, this will take some of time, but always less than 30 sec. I don't know what's the easiest solution. Any ideas? Miklos -
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Eric W. Biederman | [PATCH] nfs lockd reclaimer: Convert to kthread API |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
