search for: fs_usag

...ackup and write back cache active. >From time to time, I have sever peak io to those data disks (> 400 to 500 iops, > 70 to 100 megs/sec). With iostat, I find that it's almost a write i/o problem. How can I find to which files the OS writes ? On OSX boxes, there is a utility called fs_usage that can reports any disk activity for a particular process or all processes. Is there any utility like this on Centos ? iotop can points me to wich process, but that doesn't points me to what files are the culprits...

....tmp If I try copying the entire dir to the Debian box and try to commit from there I get the same lock and ofcourse all .svn dirs show up as :2esvn or some such thing...I suspect unicode problem? Searching on svn user list I found a msg about a similar problem where some one suggested using sudo fs_usage -w | grep svn in one terminal and then doing the commit from another. However I didn''t find any chfags (I am still not sure what chflags are) set by svn. I appreciate any help on this. TIA, bakki

common/mlutils: Unix_utils.StatVFS.statvfs: This commit implements a full-featured binding for the statvfs(3) function. We then use this to reimplement the daemon statvfs API in OCaml. Note that the Gnulib fallback is fixed in this commit. It previously referenced non-existent field names in the fs_usage struct. --- common/mlutils/unix_utils-c.c | 138 ++++++++++++++++++++++++++++--- common/mlutils/unix_utils.ml | 21 ++++- common/mlutils/unix_utils.mli | 23 +++++- daemon/Makefile.am | 11 ++- daemon/statvfs.c | 184 ------------------------------------------ daemon/s...

v1 -> v2: - Removed the f_type field from StatVFS.statvfs structure. - New function StatVFS.filesystem_is_remote, written in C. [Thinking about it, this should probably be called ?is_network_filesystem?, but I can change that before pushing]. - Use statvfs instead of fstatvfs, and statfs instead of fstatfs. - Rejigged the comments in builder/builder.ml to make them simpler

It started out as "this'll be just a simple fix ..." and turned into something a bit over-engineered in the end. Here it is anyway. Rich.

A bit off topic, but I know there are a lot of smart Mac evangelists on the list so I thought I''d pose the question here. I made the switch to OS X after Apple moved to the x86 platform. Now that VMWare can be ported to OS X, it''s a practical platform for me. I''m an ex *nix admin, so I ''get the drift''; however, I''m looking for a good guide

v2 -> v3: - Drop gnulib fallback.