Re: fsync stuck at jbd2_log_wait_commit on NVMe devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Roy,

My suggestion is to collect information from the jbd2_run_stats and
jbd2_checkpoint_stats tracepoints.

cd /sys/kernel/debug/tracing
echo 1 > events/jbd2/jbd2_run_stats/enable
echo 1 > events/jbd2/jbd2_checkpoint_stats/enable
cat trace_pipe > /tmp/traces &
tail -f /tmp/traces

The jbd2_handle_stats tracepoint can be informative, but it's also far
more voluminous.

That will give us a hint where things are getting bottlenecked.

What sort of workload is your application doing?  Is it just primarily
doing random writes into a preallocated file?  Is it creating or
deleting files?  Extending or truncating files?   etc.

	 	 	      		 - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux