Bug 77222
Summary: | Badblocks and fs corruption on Intel 845PE system and 2.4.18-17 RH rpm | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matt Dorsch <dorscm> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-11-03 16:24:34 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
Matt Dorsch
2002-11-03 16:24:28 UTC
Ok, the kernel does not seem to be the issue for the bad block indication. When I use the rescue mode, one is given three options for mounting the host filesystems: Continue (?), Read Only, and Skip. When I choose Continue, the rescue process mounts my partitions as found in /etc/fstab under /mnt/sysimage. When I do this, badblocks reports the bad block. If I just choose skip and leave it unmounted, badblocks says it's a clean partition. I think the issue is that I have had the filesystem mounted on certain tests, and not on others. Remind me to use e2fsck -c next time, eh? I think I'm going to mark this as not a bug. If I happen to run into fs errors in the future, I'll post more info. My apologies for the false alarm. (Note: it seems that even in read-only mode, something seems to be locking something on the partition. I can't unmount this partition if I have the wizard mount it.) |