[Bug 453579] Re: in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4

Jakob Unterwurzacher jakobunt at gmail.com
Thu Dec 24 11:08:15 UTC 2009


Am 2009-12-24 01:17, schrieb Goffi:
> By the way, I made a cmp of the qtmoko files, I have 2 bytes which
> differ:

Excellent! Scott, could you also post a cmp -l of a corrupted vs a good 
file?


Now, let's have some binary... (Note that cmp -l output is octal)

% cmp -l qtmoko-debian-v15.jffs2.clean qtmoko-debian-v15.jffs2.old
16070033  64 164
16070039 257 255

064 = 00110100
164 = 01110100

257 = 10101111
255 = 10101101


% cmp -l qtmoko-debian-v15.jffs2.clean qtmoko-debian-v15.jffs2.old2
12701898   0 100
12701904  47  45

000 = 00000000
100 = 01000000

047 = 00100111
045 = 00100101


You have single bit flips on the second and on the seventh bit.
This looks so much like broken memory it virtually has to be broken memory.

OTOH, if everybody sees the second and the seventh bit flip then 
probably ext4 is doing something very stupid. Again, please post your 
cmp -l results!

-- 
in-place corruption of large files *without fsck or reboot* reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list