https://bugzilla.kernel.org/show_bug.cgi?id=75881 Theodore Tso <tytso@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #1 from Theodore Tso <tytso@xxxxxxx> --- Is this something you can reliably reproduce? The log doesn't tell us anything useful, and it's not clear whether the problem is with the dm-crypt (i.e., LUKS) layer, or with the ext4 layer. All the log tells us is that we are waiting forever for a block I/O operation to finish in the jbd2 commit thread, and this is causing the lazyinit thread to give a soft lockup warning (meaning that two minutes has gone by without any forward progress taking place). I suspect the problem is in an interaction between the dm-crypt and md raid5 code, which is being tickled by the I/O patterns that you've described. But before we kick this over to the the device mapper developers, the first question is whether you can reliably reproduce the problem. -- 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
