Re: test processes are not all killed

[Dave Jones <davej@codemonkey.org.uk>]

On Thu, Aug 03, 2017 at 11:17:12AM +0800, Dai Xiang wrote:
 
 > > Ah. You might just have a *lot* of dirty pages to write out.
 > > Does iotop show that journald is writing ?
 > 
 > use iotop -o:
 > 111 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.99 %
 > [kworker/0:2] <== sometime kworker/1:1 or so on
 > sometimes more processes called kworker run, do not find trinity.
 
You can try the ftrace stuff I suggested to trace what those kworker
threads are doing, but it really sounds like it's just accumulated a ton
of dirty pages to write out.

 > > Unless you're particularly focussed on stressing filesystems, you might
 > > want to skip the sync related syscalls (fsync,fdatasync,sync,syncfs)
 > 
 > How can i skip those syscalls?

use multiple -x arguments.
This is common enough, that it might be worth adding a --no-sync
argument that just does this for all relevant syscalls.

	Dave