Bug 502970
Summary: | ext3 filesystem error reported on f10 system with crypt/soft-raid1 config | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kai Engert (:kaie) (inactive account) <kengert> | ||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 10 | CC: | agk, itamar, kernel-maint | ||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-12-18 09:29:53 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: | |||||||||
Attachments: |
|
Description
Kai Engert (:kaie) (inactive account)
2009-05-28 01:01:05 UTC
*** Bug 489783 has been marked as a duplicate of this bug. *** When I had experienced this the last time (a couple weeks ago), I booted a live CD and run a manual fsck (forced) on the file system. No problems were reported, everything clean. When I booted (today) with the f9 kernel (directly after the crash), I didn't see any reports about filesystem trouble either (during the startup messages). Only thing I saw was a "inode time future" or similar, which got fixed. So, this time, the first reported problem was in /dev/sda3, the plain partition containing the ext3 filesystem mounted at / (no crypt, no raid). Afterwards we also got problem reports for dm-1 and dm-2, two of the encrypted partitions. The current Fedora 9 and Fedora 10 kernels are both based on 2.6.27.24, so it doesn't seem right that one should work and the other not work. Or were you using an older Fedora 9 kernel when everything worked? The working Fedora 9 kernel is 2.6.27.19-78.2.30.fc9 I had problems with all the fc10 kernels. Kernels like 2.6.27.21-170.2.56.fc10 and earlier gave me problems, too. Can you post the contents of /proc/interrupts with the f10 kernel running, and also from the f9 kernel if they are different? Created attachment 346473 [details]
/proc/interrupts - fedora 9 kernel
Created attachment 346474 [details]
/proc/interrupts - fedora 10 kernel
Note, this kernel has been running only a short period of time.
(I didn't wait for the problem to show up.)
I decided to do another experiment. I'm now running the latest f9 kernel availabe from updates, and will give feedback in a couple of days. This shall answer the question: Is the problem in the kernel version later than 2.6.27.19 ? Or is the problem in the patches that are different between f9 and f10 ? (I guess the applied patches differ between f9 and f10) 2.6.27.19-78.2.30.fc9 good 2.6.27.24-78.2.53.fc9 ... currently testing 2.6.27.24-170.2.68.fc10 bad so far the latest f9 kernel works stable. I suspect the cause is contained in the differences between 2.6.27.24-78.2.53.fc9 and 2.6.27.24-170.2.68.fc10 Could this problem be related to unstable clocksource? I'm on pentium-m, dual core. My system reported "clocksource tsc unstable". Elsewhere on the web I read that it's expected the kernel will automatically switch to a more reliable clocksource. But my system didn't report any such switching to a different one. I changed my grub.conf to include clocksource=hpet on the kernel line. I just realize that I've been running the most recent f10 kernel since yesterday... Maybe that fixed my problem? (I'll report back later if the system keeps being stable.) This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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 Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |