Bug 214495
Summary: | Possible mmap dirty blocks lost in kernel-2.6.18-1.2200.fc5 ? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nick Lamb <redhat> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | axel.thimm, eli, imtiaz.rahi, jerome.benoit, pierre-bugzilla, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-22 13:50:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nick Lamb
2006-11-07 21:07:32 UTC
Today I found a small change (in our code) which seems to eliminate our symptoms. A much larger test is running and I am awaiting more information from the author of this part of the code, but I suspect that we were depending on some semantics for multiple mmap() calls that are not promised by the kernel or libc manual pages, and the actual Linux behaviour changed in 2.6.18. If so this bug is invalid and I will close it as such in the next few days. We had some further unexplained problems, where seemingly data was written via an mmap() and then an earlier version was found on disk. Forcing an upgrade to the 2.6.19.2 based 2.6.19-1.2895 from the FC6 updates eliminated all symptoms on our test cluster. Thus it seems likely that all along we were seeing another example of the famous ext3 + mmap bug Linus fixed in 2.6.19.2 Can FC5 users get a backport of 2.6.19.2 or at least of Linus' ext3 mmap fix for Fedora Core 5 ? I will probably try to do my own RPM rebuild of the FC6 source RPM, but we probably won't be the only ones affected by this, so it make sense to try to have this as an update for other users too. FC5 update to upstream kernel 2.6.19.3 is in the works. *** Bug 227194 has been marked as a duplicate of this bug. *** *** Bug 211254 has been marked as a duplicate of this bug. *** Our rebuild of 2.6.19.2 works, we have not seen any data corruption in the six weeks or so since we upgraded production systems to this version. I have no reason to assume it's any different for the version Red Hat shipped and no desire to disrupt production machines by changing to an almost identical kernel. Hence resolving as fixed by ERRATA |