Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 226963
Summary: | mkfs.ext3 says everything is ok even if disk failed. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Laurent Wandrebeck <l.wandrebeck> |
Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | kzak, sct |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-07-23 18:19:38 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
Laurent Wandrebeck
2007-02-02 10:18:21 UTC
ok, so this bug is what mkfs does in the face of IO errors... I'll have to take a look at the error checking. Out of curiosity, what does subsequent mount or fsck say? The root cause is unknown, looks like you have ATA problems... Actually, there is not much that mkfs can do here; it is doing buffered writes (which is fine) which will actually be flushed to disk at a later time. If those later attempts to flush data fail, mkfs won't know; it may well have already exited; there is no feedback possible. Unless mkfs were to use direct IO it would not catch this sort of error. But, this is true of any application which does buffered writes. I'm going to close this as NOTABUG; I think the only real problem here is that you have a failing disk. |