Forum Topic - Identifying processes which are writing "too much": (2 Items)
   
Identifying processes which are writing "too much"  
Hi all,
To help identify processes which are writing excessively to flash storage (and therefore contributing to premature 
failure), I've been tasked with developing a utility which can report on a per-process basis the number of bytes written
 during a given boot cycle. I am considering a few options:
1. Use QNX's profiling tools.  From what I know of them, I don't think I can get what I need from them (i.e., total # of
 bytes written by every process), but maybe I'm wrong about that?
2. Implement a file system pass-through resource manager to keep track of every write in a given path. This approach 
would provide all the information I need, but it seems like a lot of work with some nasty corner cases.
3. Use inotify to monitor files & directories in a given path. This seems like a non-starter because I don't see a way 
to correlate writes to the process that is performing them.

A few general points: 
* Performance isn't an issue as long as the system can still function somewhat normally. This utility would not be part 
of a normal running system.
* I'm using SDP 7.1.

Does anyone have any thoughts about whether any of the options I've listed could be viable or suggestions for other 
approaches I haven't mentioned? Thanks in advance for any help!

Paul Kerchen
Re: Identifying processes which are writing "too much"  
Update: I decided on using the inotify approach, even though it doesn't provide information about which process is doing
 the writing. I'll have to deduce process information from the paths that are being written to. A file system resource 
manager would give me the process information, but the risks of that approach far outweigh the convenience of having the
 process information.