https://bugzilla.kernel.org/show_bug.cgi?id=39072 Lars Stokholm <lars.stokholm@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lars.stokholm@xxxxxxxxx --- Comment #2 from Lars Stokholm <lars.stokholm@xxxxxxxxx> 2011-07-10 20:08:51 --- I just wanted to say that I agree --- Comment #3 from Lars Stokholm <lars.stokholm@xxxxxxxxx> 2011-07-10 20:13:38 --- Oops. Sorry, I'm very new to this bug list, I committed before I should have. I just wanted to say that I agree with you Theodore. Going into single user mode helps. In fact just killing off my daemons (syslog-ng, cron and so on) along with X was enough. I didn't have to go to single user mode. --- Comment #4 from Theodore Tso <tytso@xxxxxxx> 2011-07-11 03:15:46 --- Created an attachment (id=65212) --> (https://bugzilla.kernel.org/attachment.cgi?id=65212) Journal tracepoint patch The following patch should help people figure out which process is responsible for starting an jbd2 transaction handle. After applying the patch, enable it via: echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_journal_start/enable echo 1 > /sys/kernel/debug/tracing/events/jbd2/jbd2_run_stats/enable cat /sys/kernel/debug/tracing/trace_pipe ... and wait. (All of this assumes you have ftrace enabled, of course). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
