https://bugzilla.novell.com/show_bug.cgi?id=750927
https://bugzilla.novell.com/show_bug.cgi?id=750927#c1
--- Comment #1 from Jan Kara 2012-03-08 09:49:41 UTC ---
Thanks for report! Do you think commit e44718318004a5618d1dfe2d080e2862532d8e5f
is the culprit just because you see jbd2/sda3-8 doing work or do you have more
reasons? Because I don't see how e44718318004a5618d1dfe2d080e2862532d8e5f could
cause your problem and jbd2/sda3-8 will be active whenever anybody will write
anything to the filesystem... So I think it's just a messenger.
Can you run:
echo 1 >/sys/kernel/debug/tracing/events/ext4/ext4_mark_inode_dirty/enable
echo 1 >/sys/kernel/debug/tracing/events/ext4/ext4_write_begin/enable
cat /sys/kernel/debug/tracing/trace_pipe
and you should see which process is dirtying inodes or writing something. Paste
the output here and hopefully we should be able to do more...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.