Bug 220711
Summary: | ext3 file system corruption | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pawel Salek <pawsa> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | esandeen, umar, wtogami |
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: | 2007-01-27 15:15:31 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
Pawel Salek
2006-12-24 00:26:55 UTC
I have the same/similar setup: =================================================================== # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 63197036 9496128 50438856 16% / /dev/sda3 101105 11311 84573 12% /boot tmpfs 1990808 0 1990808 0% /dev/shm =================================================================== having a x86_64 system running kernel-2.6.18-1.2868.fc6, which I rebuild by only selecting em64t processor option and turning on kernel debug options. I have recompiled many rpm packages with this kernel already and did not encounter ext3 corruption. Could it be your disk acting up? Sammy Well, I cannot tell for sure it is the hardware but SMART reports no error. It may be just as well my 5 years old motherboard or some interaction between PATA harddisk and DVD burner sitting on the same cable... I'd probably chalk it up to hardware, but it might be interesting to at least post some details on how your fs is corrupted, i.e. what fsck found. If SMART thinks things are ok, you might consider seeing if the driver mfgr has their own test bootdisk, sometimes that's more useful. I'd also scour the logs for any messages about hda if you are certain that the vgroup for the corrupted fs only contains hda. Seeing { DriveReady SeekComplete Error } on any drive in your system doesn't give me a good feeling about the reliability of the hardware in this box though :) -Eric I would close this bug for now but I do not know what the proper resolution code should be. I have not been able to reproduce the disk corruption since. SMARTD signals nothing, forced disk checks reveal no new problems. The DriveReady errors are still there - but they occur only*once* per session, when HAL service is being started. Current kernel print additionally information: ide: failed opcode was: 0xb0 just after the error line. I actually seem to recall seeing these one-time hdX spews on boot with certain drives, as well as someone saying it was just that the drive didn't support a certain feature and the message wasn't actually anything to worry about (aside from looking scary). Aha, there's the bug I was after: bug 214502, particularly the 4th comment from Dave Jones. Yes, my remaining problem looks pretty much like the one described in bug 214502. It is very likely the disk corruption was unrelated. |