https://bugzilla.kernel.org/show_bug.cgi?id=194739 Ivan Kalvachev (iive@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |CODE_FIX --- Comment #1 from Ivan Kalvachev (iive@xxxxxxxxx) --- With kernel-4.10.2 I cannot reproduce the bug anymore. The following commit looks like it might be the one fixing the issue: --- commit 011fe6ade610c2ca5a609c83c509f1fc8e4c8b7f Author: Roman Pen <roman.penyaev@xxxxxxxxxxxxxxxx> Date: Sun Jan 8 21:00:35 2017 -0500 ext4: do not polute the extents cache while shifting extents commit 03e916fa8b5577d85471452a3d0c5738aa658dae upstream. Inside ext4_ext_shift_extents() function ext4_find_extent() is called without EXT4_EX_NOCACHE flag, which should prevent cache population. This leads to oudated offsets in the extents tree and wrong blocks afterwards. Patch fixes the problem providing EXT4_EX_NOCACHE flag for each ext4_find_extents() call inside ext4_ext_shift_extents function. Fixes: 331573febb6a2 --- -- You are receiving this mail because: You are watching the assignee of the bug.
