Bug 66308
Summary: | Filesystem corruption under ext3 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John <jsk29> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Aaron Brown <abrown> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-06-10 07:15:59 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
John
2002-06-07 14:03:07 UTC
"I/O error" usually means that the disk has a bad sector and the filesystem cannot read data from it. Journaling filesystems protect you from the effects of a crash *assuming the data is still intact on disk*. Ext3 does survive a crash during recovery perfectly well. However, if you get I/O errors and bad sectors on disk, then there's nothing that the journaling filesystem can do to correct that. e2fsck might fix it simply by removing the unreadable files completely. I/O errors also occasionally occur because there is corrupt data on disk even if that data is still readable. Journaling relies on the data that the filesystem sent to disk being written correctly. If the hardware is overheating then it is quite possible for the data to get corrupted, and in that case again the filesystem is powerless to protect you: there's no point in writing a journal carefully to disk if the memory, controller, cpu or disk drive is flipping bits in the journal on its way. Again, a full fsck may be required to sort out the mess afterwards. |