[Bug 14354] Bad corruption with 2.6.32-rc1 and upwards

[bugzilla-daemon@bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=14354





--- Comment #63 from Alexey Fisher <bug-track@fisher-privat.net>  2009-10-16 15:27:54 ---
First result with v2.6.31:
I made some scripts to make me kill my pc easier. Now i log fsck, dmesg and
md5sum every time after i kill it.
2.6.31 acting worse in this situation than 2.6.32 do. On mount readonly, kernel
trying to recovery fs (... 6 orphan inodes deleted ... recovery complete) fsck
-y -f return no warnings (only  "FILE SYSTEM WAS MODIFIED"). After reboot there
is many _corrupt_ modules, files are existing but do not match (md5sum) with
original files... diff <(xxd file_corrupt) <(xxd file_orig) show about 30% of
difference. I expected fsck will remove korrupted files warn me about this.

I do not using sync in my script. This will be really nice if kernel did sync
before pc die.

I will test now v2.6.32-rc4 again with md5sum and see the difference. After
this i will try auto_da_alloc=0

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.