| |||||||||||||
A nasty file corruption bug - fixedA nasty file corruption bug - fixedPosted Jan 1, 2007 9:57 UTC (Mon) by bronson (subscriber, #4806)In reply to: A nasty file corruption bug - fixed by arjan Parent article: A nasty file corruption bug - fixed
On the other hand, because nobody noticed this bug for four years, I don't think another week or two will cause anyone much trouble.
(Log in to post comments)
A nasty file corruption bug - fixed Posted Jan 1, 2007 10:08 UTC (Mon) by arjan (subscriber, #36785) [Link] people noticed.. in hindsight. Suddenly a series of db4 reports show up with people saying they see this regularly and it's now gone away with the fix...
A nasty file corruption bug - fixed Posted Jan 1, 2007 21:23 UTC (Mon) by bgoglin (subscriber, #7800) [Link] Nobody noticed previously because the bug was hidden. But some changes in 2.6.19 (dirty page balancing, causing writeback to happen earlier) revealed the bug, making it occur much more frequently. Everybody using 2.6.19 should probably downgrade to an earlier kernel or use an upcoming 2.6.19.2 with the fix.
A nasty file corruption bug - fixed Posted Jan 1, 2007 21:29 UTC (Mon) by ber (subscriber, #2142) [Link] With Cyrus imapd, especially within the Kolab Server we saw file corruptions which could be related to mmap problems. It occurrs rarely enough that we do not have a testcase. Details at kolab/issue840. So I would welcome patches for older kernels and referable information on how long this bug has been in there.
A nasty file corruption bug - fixed Posted Jan 1, 2007 23:05 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link] it seems that this bug has been in the kernel since at least the 2.5 timeframe, the change in 2.6.19 just made it far easier to hit.
|
|||||||||||||