http://bugzilla.kernel.org/show_bug.cgi?id=14354 Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aneesh.kumar@xxxxxxxxxxxxxx | |.com --- Comment #153 from Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx> 2009-10-30 10:26:23 --- Hi Linus, Eric, There are two changes that went in after 2.6.31 that i am doubtful. 0d34ec62e18984ac9476208660372306ef54e70d That changes the ext4_file_write to not do a journal commit if inode doesn't have dirty flag set. Jan Kara actually found other issues with the ext4 sync code path and have posted a patch here( MID 1256647729-29834-1-git-send-email-jack@xxxxxxx ) http://article.gmane.org/gmane.comp.file-systems.ext4/16126. But that should not result in multiple claimed blocks. 487caeef9fc08c0565e082c40a8aaf58dad92bbb The changes allowed to release i_data_sem during truncate. That implies we could allow block allocation while we are doing truncate. I did a patch to drop prealloc space once we reacquire i_data_sem. Posted in comment 123 of this bug. But that didn't fix the corruption. So may be we want to test backing out 487caeef9fc08c0565e082c40a8aaf58dad92bbb and applying patch at http://article.gmane.org/gmane.comp.file-systems.ext4/16126 and see if we are able to reproduce. -aneesh -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- 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
