Bug 214491 - megaraid_sas : disk seem forbiden after some time "ext3fs : impossible to write journal"
Summary: megaraid_sas : disk seem forbiden after some time "ext3fs : impossible to wri...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-07 20:44 UTC by Thierry Leurent
Modified: 2007-11-17 01:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-01 20:45:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Thierry Leurent 2006-11-07 20:44:22 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)

Description of problem:
On a PowerEdge 2900 with a RHEL 4 (updated), I have one very strange trouble.
After 2 weeks of non-stop work, I have had a message that tell somethings like "ext3fs : Impossible to write journal".
The message was displayed so quickly that I can't log me.
I restart the system with a power shutdown, and now everythings is good from 5 days.
I have a kernel 2.6.9-42.0.3 with the megaraid_sas driver in version 00.00.02.03.


Version-Release number of selected component (if applicable):
kernel-2.6.9-42.0.3

How reproducible:
Couldn't Reproduce


Steps to Reproduce:
1.
2.
3.

Actual Results:


Expected Results:


Additional info:
Comment 1 Thierry Leurent 2006-11-13 07:47:07 UTC 
The message is "Ext3-fs error (device dm-4) in start_transaction: Journal had 
aborted"
Comment 2 Eric Sandeen 2007-01-27 05:53:38 UTC 
Were there other error messages before the message in comment #1?
Comment 3 Jay Fenlason 2007-10-01 20:45:36 UTC 
There have been no replies to this in over six months, so I'm closing it.  If 
you have the needed data, please attach it to this bug and reopen it.
Note You need to log in before you can comment on or make changes to this bug.