Bug 247205
Summary: | System hung with Ext-fs error (device dm-5) in start_transaction: Journal has aborted | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | JB Segal <jb> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Martin Jenner <mjenner> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4.4 | ||
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: | 2008-12-04 21:57:58 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
JB Segal
2007-07-05 23:47:19 UTC
After reboot, was there anything in the system logs prior to the "journal has aborted" message? Or was it the root filesystem which had the problem, and so I suppose no further messages were logged to disk...? This has been in needinfo for over a year; closing. |