Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 227361

Summary: lvremove snapshot do a kernel panic
Product: Red Hat Enterprise Linux 4 Reporter: Martial Paupe <martial.paupe>
Component: lvm2Assignee: Milan Broz <mbroz>
Status: CLOSED DUPLICATE QA Contact: Corey Marthaler <cmarthal>
Severity: high Docs Contact:
Priority: medium    
Version: 4.4CC: agk, dwysocha, jbrassow, mbroz, prockai, pvrabec
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-05 17:08:29 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
proccedure to create and remove snapshot
none
log of problem none

Description Martial Paupe 2007-02-05 16:38:00 UTC 
Description of problem:
I use LVM snapshot to do backup. But when the backup finish it remove snapshot
and a kernel panic occurs.

Version-Release number of selected component (if applicable):
lvm2-2.02.06-6.0.RHEL4
kernel-smp-2.6.9-42.0.3.EL

How reproducible:
Intermittent, not easily reproducable.

Steps to Reproduce:
N/A
  
Actual results:


Expected results:


Additional info:
Comment 1 Martial Paupe 2007-02-05 16:38:00 UTC 
Created attachment 147366 [details]
proccedure to create and remove snapshot
Comment 2 Martial Paupe 2007-02-05 16:39:54 UTC 
Created attachment 147367 [details]
log of problem
Comment 3 Milan Broz 2007-02-05 17:08:29 UTC 
Known issue with removing full snapshot - see bug 204791.

Also please check space for snapshot - you are probably allocating too small
area (see i/o error in log, probably caused by snapshot overfill).

*** This bug has been marked as a duplicate of 204791 ***