Bug 91094
Summary: | e2fsck fails causing boot to fail, among other issues | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Bill Catlan <wcatlan> |
Component: | installer | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | gehicks |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-13 21:21:02 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
Bill Catlan
2003-05-17 22:04:48 UTC
I encountered the same e2fsck boot-time hangup (RH9) by setting /etc/fstab options: LABEL=/ / ext3 defaults,sync 1 1 (duh, that probably doesn't make much sense for ext3?) Additionally, this happens when booting kernel-2.4.20-18.9 but does not happen when booting 2.4.20-8 (same fstab entries) (this is with the probably-wrong 'default,sync' fstab entry on ext3 2.4.20-18.9) 'shutdown -f ...' allows a clean restart (fsck skips the already mounted filesystem) and all is well. Just 'shutdown ...' 100% failure for this case here. fsck - already mounted filesystem I imagine quite a few folks may hit this issue upgrading though. It's pretty easy to trash an installation if one isn't thinking too clearly (like me :-) Added some code to handle some of this better in cvs |