search for: ocfs2_inode_cache

...A simple `ls -Rn' on a filesystem with lots of files makes the box leak so much RAM that the OOM killer starts to kick in. With slab alloc debugging turned on, we see this: # mount; ls -Rn; wait some seconds; Ctrl-C [root@lnxp-1038:/backend1]$ cat /proc/slab_allocators | egrep '(size.512|ocfs2_inode_cache)' | grep ocfs | sort -k 2 -n size-512: 1 o2hb_heartbeat_group_make_item+0x1b/0x79 [ocfs2_nodemanager] size-512: 1 o2hb_map_slot_data+0x22/0x2fa [ocfs2_nodemanager] size-512: 1 ocfs2_initialize_super+0x55e/0xd7f [ocfs2] size-512: 26439 ocfs2_dentry_attach_lock+0x2d1/0x423 [ocfs2] ocfs2_inode_cac...

...nfsd4_files 0 0 36 101 1 nfsd4_stateowners 0 0 344 11 1 rpc_buffers 8 8 2048 2 1 rpc_tasks 8 15 256 15 1 rpc_inode_cache 0 0 512 7 1 ocfs2_lock 152 203 16 203 1 ocfs2_inode_cache 12484 12536 896 4 1 ocfs2_uptodate 1381 1469 32 113 1 ocfs2_em_ent 37005 37406 64 59 1 dlmfs_inode_cache 1 6 640 6 1 dlm_mle_cache 10 10 384 10 1 configfs_dir_cache 33 78 48 78 1 fib6_nodes...

Hi 2 all ! I have problems with concurrent filesystem actions on a ocfs2 filesystem which is mounted by 2 nodes. OS=RH5ES and OCFS2=1.2.6 F.e.: If I have a LV called testlv which is mounted on /mnt on both servers and I do a "dd if=/dev/zero of=/mnt/test.a bs=1024 count=1000000" on server 1 and do at the same time a du -hs /mnt/test.a it takes about 5 seconds for du -hs to execute: 270M

The following series of patches attempts to detach metadata I/O from struct inode. They are currently tied together pretty tightly. Metadata reads happen via the ocfs2_read_blocks() functions, writes via both jbd2 and ocfs2_write_blocks(). - Each inode has a cache of associated metadata blocks stored on its ip_metadata_cache member. The ocfs2_read/write_blocks() functions take a struct