https://bugzilla.kernel.org/show_bug.cgi?id=71791 Zheng Liu <gnehzuil.liu@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gnehzuil.liu@xxxxxxxxx --- Comment #2 from Zheng Liu <gnehzuil.liu@xxxxxxxxx> --- I guess that the journal mode is 'data=ordered', right? Could you please try to switch the journal mode to 'data=writeback' and look at whether or not the problem can be reproduced? In our product system, we met a hang which is caused by 'data=ordered' under a heavy IO workload. When the user uses 'rm' command to delete a file, ext4_begin_ordered_truncate() should be called with 'data=ordered' and it could trigger write back kernel thread to write out the dirty data. Then truncate_inode_pages() will wait on write back. Regards, - Zheng -- 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
