Bug 596009
| Summary: | Possible ext4 anomalies | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | George R. Goffe <grgoffe> |
| Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | anton, dougsland, esandeen, gansalmon, itamar, Jacek.Pliszka, jonathan, kernel-maint, kmcmartin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-15 21:57:18 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
George R. Goffe
2010-05-26 06:23:06 UTC
Have you had crashes or powerlosses before you saw this happen? Or the machine has been up this whole time and you suddenly have the content lost? What does poweroff do? :) Does the root fs fsck cleanly? (touch /.forcefsck will make it check next boot, IIRC) No crashes or power losses. I'll give your /.forcefsck trick and reboot in a while. Does this work on all file systems? THANKS! This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Howdy, I'd like to leave this open just in case. I'll be migrating to FC13 in the near future. So far, the problem has not happened again. If you MUST close it then please feel free to do so. Thanks, George... Hi! I just got the same error in F14. My wife was using OpenOffice writer - she saves regularly. Then suddenly we had power outage. After it the document she was working on for the last 5 hours and was saving regularly was gone and empty. OpenOffice writer was not able to recover it. Before F14 we used ext3 for /home - never had problems like this - OO always was able to recover. With F14 we are using ext4 - I guess this might be ext4 bug. Howdy, I have not seen this problem other than the two times on FC12. I have one system at FC12 and one at FC14. I'll keep my eyes on what's going on on this system that might provide clues to this behavior and, of course, report them immediately. Is this the right place for FC14 bugs? George... ext3 essentially syncs every 5s - data=ordered (default) + 5s journal commit pushes file data out more often than "normal" It is most likely that the application is not doing proper data integrity management... even in the case of a manual save, it matters what OO is doing during periodic saves, etc. I'm not aware of any deficiencies in ext4's fsync/data integrity handling... In each specific case here it would be good to do something like strace OO, and see what file IO calls it's doing (writes, truncates, opens, closes, renames, fsyncs, etc...) -Eric George, are you still seeing these issues? If not I don't know where to go with this bug... Jacek, losing buffered data after a power loss sounds like a different issue, and more likely related to OO doing something bad with data integrity. I'll probably close this bug unless the mystery George reported is still being mysterious... Eric, I think we can close this one. I have not (so far) seen any problems like this. I'm on fc14 now... It's rough... KDE/X11 are having serious problems... a whole slew of other X11 stuff's failing... I use startx > startx.log 2>&1 and it's horrible... + X11 dumps core when you exit KDE... I have not made many bugs yet... but will. Regards and thanks for your patience. George... Current release seems to work, so closing. |