Bug 491900
| Summary: | While attempting iSCSI installation - Filesystem error detected, cannot continue. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> |
| Component: | anaconda | Assignee: | Joel Andres Granados <jgranado> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dlehman, esandeen, jgranado, jturner, pjones, rmaximo, tcallawa, vanmeeuwen+fedora |
| 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: | 2009-05-06 21:23:18 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 495965 | ||
|
Description
James Laska
2009-03-24 15:30:43 UTC
I guess that we just need to do some File System checks after the mount fails. If we find that the filesystem is corrupt we ask for user intervention. When in kickstart we do what initlabel tells us. There isn't really any mounting going on in that block of code AFAIK. I think we need to figure out where these can come from and resolve them at a lower level (like somewhere in the DeviceTree). If the filesystem is broken we should either just log it and hope for the best or replace the format with the format base class ("Unknown"). In the latter case, we aren't changing anything -- we're just changing the way we show the filesystem type since it is apparently unusable.
This message is no longer in the code. There were changes that would address this issue. pls retest and move to assigned if the behavior persists. |