Noah Meyerhans <[EMAIL PROTECTED]> wrote: > > Active:12382 inactive:280459 dirty:214 writeback:0 unstable:0 free:2299 > slab:220221 mapped:12256 pagetables:122
Vast amounts of slab - presumably inode and dentries. What sort of local filesystems are in use? Can you take a copy of /proc/slabinfo when the backup has run for a while, send it? It's useful to run `watch -n1 cat /proc/meminfo', see what the various caches are doing during the operation. Also, run slabtop if you have it. Or bloatmeter (http://www.zip.com.au/~akpm/linux/patches/stuff/bloatmon and http://www.zip.com.au/~akpm/linux/patches/stuff/bloatmeter). The thing to watch for here is the internal fragmentation of the slab caches: dentry_cache: 76505KB 82373KB 92.87 93% is good. Sometimes it gets much worse - very regular directory patterns can trigger high fragmentation levels. Does increasing /proc/sys/vm/vfs_cache_pressure help? If you're watching /proc/meminfo you should be able to observe the effect of that upon the Slab: figure. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
