Posted Dec 21, 2006 10:43 UTC (Thu) by cate (subscriber, #1359)
[Link]
IIRC from the reporter, the bug corrupts only the downloaded file, and the bittorent client finds the error (wrong checksum). So it should not got unnoticed, and it doesn't corrupt other files.
A gnarly 2.6.19 file corruption bug
Posted Dec 21, 2006 12:11 UTC (Thu) by Randakar (guest, #27808)
[Link]
Looking at the link to Linus' testcase, it seems to be 'rtorrent'.
"Btw, here's a simpler test-program that actually shows the difference
between 2.6.18 and 2.6.19 in action, and why it could explain why a
program like rtorrent might show corruption behavious that it didn't show
before."
rtorrent
Posted Dec 21, 2006 14:17 UTC (Thu) by Webexcess (subscriber, #197)
[Link]
rtorrent is a very nice program.
I've also found that it's a great burn-in for a system. It's really good at testing ram, cpu and network (for lots of "light" connections). Apparently it can be a good filesystem test too!
A gnarly 2.6.19 file corruption bug
Posted Dec 21, 2006 23:17 UTC (Thu) by k8to (subscriber, #15413)
[Link]
Ah, I suspected as much. I use that program regularly, and it makes heavy use of mmap.
I guess I'll move back to 2.6.18 for now.
A gnarly 2.6.19 file corruption bug
Posted Jan 1, 2007 18:15 UTC (Mon) by erich (subscriber, #7127)
[Link]
Note that the Debian and Ubuntu (apparently) 2.6.18 kernels have the same problem. Maybe other distributions as well.
But I guess there will be a fixed 2.6.18 kernel coming in any day now.
A gnarly 2.6.19 file corruption bug
Posted Jan 2, 2007 20:30 UTC (Tue) by rvfh (subscriber, #31018)
[Link]
Ubuntu does not use 2.6.18 nor 2.6.19, so Ubuntu users are safe
AFA this bug is concerned.