Bug 132430 - AS2.1 + Secure Path 3.0C + Veritas Vxfs/Vxvm snapshot=kernel panic
AS2.1 + Secure Path 3.0C + Veritas Vxfs/Vxvm snapshot=kernel panic
Status: CLOSED DUPLICATE of bug 78616
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel (Show other bugs)
2.1
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-13 08:14 EDT by Fredrik Backman
Modified: 2007-11-30 17:06 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:05:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screen dump of kernel panic (56.20 KB, text/plain)
2004-09-13 08:17 EDT, Fredrik Backman
no flags Details

  None (edit)
Description Fredrik Backman 2004-09-13 08:14:48 EDT
Description of problem: During a backup ie hard I/O (we do a vxfs 
snapshot volume and backs it up) I get a kernel panic almost every 
night. Suspect scsi_mod for this.

Version-Release number of selected component (if applicable):
RH AS2.1 Update 3, kernel 2.4.9-e35
qla2312 driver version 6.06.50-29
Secure Path 3.0C
Veritas Foundation Suite 2.2
VRTSvxvm-3.2-update4_RH
VRTSvxfs-3.4.3-RH


How reproducible:


Steps to Reproduce:
1. Set up above system.
2. Make a VXfs snapshot volume, mount it and backup mounted filesystem
3. Kernel Panic
  
Actual results:
Kernel Panic


Expected results:
Kidding right?

Additional info:
Comment 1 Fredrik Backman 2004-09-13 08:17:22 EDT
Created attachment 103782 [details]
Screen dump of kernel panic
Comment 2 Arjan van de Ven 2004-09-13 08:42:33 EDT
please try to reproduce this without bin only modules or contact RH
support so that they can escalate this to the respective vendors.

*** This bug has been marked as a duplicate of 78616 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:05:35 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.