https://bugzilla.kernel.org/show_bug.cgi?id=203247 Bug ID: 203247 Summary: jbd2 gets stuck at jbd2_journal_commit_transaction frequently Product: File System Version: 2.5 Kernel Version: 4.9.86 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: ext3 Assignee: fs_ext3@xxxxxxxxxxxxxxxxxxxx Reporter: pankajcabs@xxxxxxxxx Regression: No Created attachment 282263 --> https://bugzilla.kernel.org/attachment.cgi?id=282263&action=edit dmesg file I am noticing jbd2 getting blocked on commit_transaction causing processes to go in D state for good amount of time, it comes out of that state automatically. I am dumping the sysrq-w and sysrq-l Apr 10 15:47:23 ex-etp3 kernel:sysrq: SysRq : Show Blocked State Apr 10 15:47:23 ex-etp3 kernel: task PC stack pid father Apr 10 15:47:23 ex-etp3 kernel:jbd2/sda10-8 D 0 2573 2 0x00000000 Apr 10 15:47:23 ex-etp3 kernel: ffff8818347c97c0 0000000000000000 ffff88101c9d0140 ffff8817ff898080 Apr 10 15:47:23 ex-etp3 kernel: ffff88101fd17e40 ffff8817fec47b38 ffffffff816bcf06 ffff8807ff66b040 Apr 10 15:47:23 ex-etp3 kernel: ffff8817ff898080 7fffffffffffffff ffffffff81c06930 ffffffff816bdae0 Apr 10 15:47:23 ex-etp3 kernel:Call Trace: Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bcf06>] ? __schedule+0x1b6/0x570 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bdae0>] ? bit_wait+0x50/0x50 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bd2f4>] ? schedule+0x34/0x80 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bfd25>] ? schedule_timeout+0x165/0x290 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81264366>] ? generic_make_request+0x116/0x290 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bdae0>] ? bit_wait+0x50/0x50 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bcce9>] ? io_schedule_timeout+0x99/0x100 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bdaf2>] ? bit_wait_io+0x12/0x60 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bd725>] ? __wait_on_bit+0x55/0x80 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bdae0>] ? bit_wait+0x50/0x50 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816bd919>] ? out_of_line_wait_on_bit+0x79/0xa0 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff8109d970>] ? autoremove_wake_function+0x30/0x30 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff8122301f>] ? jbd2_journal_commit_transaction+0x198f/0x1b00 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81085b41>] ? finish_task_switch+0x81/0x1f0 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81226150>] ? kjournald2+0xc0/0x260 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff8109d940>] ? wake_up_bit+0x20/0x20 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81226090>] ? commit_timeout+0x10/0x10 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81080922>] ? kthread+0xd2/0xf0 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816c5645>] ? __clear_rsb+0x25/0x3d Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81080850>] ? kthread_park+0x50/0x50 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff81068beb>] ? SyS_exit_group+0xb/0x10 Apr 10 15:47:23 ex-etp3 kernel: [<ffffffff816c0ff4>] ? ret_from_fork+0x44/0x70 -- You are receiving this mail because: You are watching the assignee of the bug.
