Theodore Ts'o 9924a92a8c ext4: pass context information to jbd2__journal_start()
So we can better understand what bits of ext4 are responsible for
long-running jbd2 handles, use jbd2__journal_start() so we can pass
context information for logging purposes.

The recommended way for finding the longer-running handles is:

   T=/sys/kernel/debug/tracing
   EVENT=$T/events/jbd2/jbd2_handle_stats
   echo "interval > 5" > $EVENT/filter
   echo 1 > $EVENT/enable

   ./run-my-fs-benchmark

   cat $T/trace > /tmp/problem-handles

This will list handles that were active for longer than 20ms.  Having
longer-running handles is bad, because a commit started at the wrong
time could stall for those 20+ milliseconds, which could delay an
fsync() or an O_SYNC operation.  Here is an example line from the
trace file describing a handle which lived on for 311 jiffies, or over
1.2 seconds:

postmark-2917  [000] ....   196.435786: jbd2_handle_stats: dev 254,32 
   tid 570 type 2 line_no 2541 interval 311 sync 0 requested_blocks 1
   dirtied_blocks 0

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2013-02-08 21:59:22 -05:00
..
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-11-16 11:20:42 -06:00
2013-01-03 11:41:43 -08:00
2012-12-20 17:40:20 -08:00
2012-12-20 14:00:01 -05:00
2012-12-20 18:40:00 -05:00
2012-12-20 18:40:52 -05:00
2012-12-20 18:40:53 -05:00
2012-12-20 18:40:53 -05:00
2012-12-20 18:40:54 -05:00
2012-12-20 18:40:54 -05:00
2012-12-20 18:40:55 -05:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2013-01-03 15:57:14 -08:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-12-17 17:15:26 -08:00
2012-12-20 14:00:01 -05:00
2012-10-22 08:50:37 +03:00
2012-10-29 09:00:57 -07:00
2012-10-09 15:52:31 +09:00
2013-01-03 15:57:16 -08:00
2012-11-28 21:49:02 -05:00
2012-12-20 18:46:29 -05:00
2012-10-09 18:35:22 -04:00
2012-12-11 13:43:42 +09:00
2012-09-26 21:08:52 -04:00
2012-12-17 17:15:27 -08:00
2013-01-06 20:58:13 -08:00
2012-12-20 18:50:01 -05:00
2012-10-09 23:33:39 -04:00