On Fri, Dec 05, 2008 at 05:15:09PM -0500, Jim Mauro wrote:
> The problem you're running into is disk IO operations tend to occur
> asynchronously to the thread that initiated the IO, so when the IO
> provider probe fires, execname shows the process name for PID 0.
> This is not uncommon when chasin
The problem you're running into is disk IO operations tend to occur
asynchronously to the thread that initiated the IO, so when the IO
provider probe fires, execname shows the process name for PID 0.
This is not uncommon when chasing disk and network IOs. You
need to capture the write further up th
Hello,
Running the iotop dtrace script, we see many entries like
UIDPID PPID CMD DEVICE MAJ MIN DBYTES
0 3 0 fsflush md3 85 3 W 512
...
...
0 0 0 schedssd22 118 176 W 80538112
0
