Bug 220434

Summary: snapshot LVM [Assertion failure in journal_flush_Rsmp_e2f189ce() at journal.c:1356: "!journal->j_checkpoint_transactions"
Product: Red Hat Enterprise Linux 3 Reporter: Martial Paupe <martial.paupe>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 3.8   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 18:39:30 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:
Attachments:
Description Flags
item in message log none

Description Martial Paupe 2006-12-21 09:24:37 UTC 
Description of problem:
When I create snapshot I have a "Assertion failure in
journal_flush_Rsmp_e2f189ce() at journal.c:1356:
"!journal->j_checkpoint_transactions"" and a kernel panic in message log.

How I can fix that.

Version-Release number of selected component (if applicable):
kernel 2.4.21-47.0.1.ELsmp
lvm 1.0.8-14

Actual results:
I can't remove snapshot

Expected results:


Additional info:
"http://www.linuxquestions.org/questions/showthread.php?t=383422"
Comment 1 Martial Paupe 2006-12-21 09:24:38 UTC 
Created attachment 144170 [details]
item in message log
Comment 2 RHEL Program Management 2007-10-19 18:39:30 UTC 
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.