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

[DjznBR]

I believe the bug title has been changed once or twice, but let me re-
quote here what Scott reported:

"There are worrying reports of filesystem corruption on ext4 in karmic.
Scott says:

12:36 < Keybuk> this whole ext4 thing is worrying me
12:36 < Keybuk> I just downloaded an iso image, md5sum didn't match
12:36 < Keybuk> downloaded it into an ext3 partition, matched just fine
12:59 < Keybuk> and I know mvo has seen bugs with corrupted .debs in /var/cache/apt/archives
12:59 < Keybuk> which seems to imply its any file large enough to use lots of extents"


Well, that's exactly what happened on a fresh Lucid install, using ext4 partition. 

It may be neither an issue with ext4 itself, nor an issue with kernel
version or patch.

I think this is related to "Transmission" application. Because reports
are that the corruption takes place when torrents are downloaded. And
this is what exactly happened.  In some ways it may be that Transmission
is not handling ext4 well. And it's very subtle, since a "file recheck"
on finished torrents may just reconscrut the proper MD5SUM.

-- 
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 in ubuntu.