Bug 221666 - NFS kernel panic when virtual IP is moved
NFS kernel panic when virtual IP is moved
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ric Wheeler
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-05 17:33 EST by Robert Peterson
Modified: 2010-03-16 13:26 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-16 13:26:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Several instances of kernel panic from my test (16.43 KB, text/plain)
2007-01-05 17:33 EST, Robert Peterson
no flags Details

  None (edit)
Description Robert Peterson 2007-01-05 17:33:24 EST
Description of problem:
When recreating bug #190756, I kept getting kernel panics with
or without my patch to fix the problem.

Version-Release number of selected component (if applicable):
RHEL4 U4

How reproducible:
Happens 25% - 50% of my attempts to recreate 190756.

Steps to Reproduce:
1. Export a GFS file system on a 3-node cluster running RHEL4 U4
   In my case, roth-01, roth-02 and roth-03.
2. Create a virtual IP xx.xx.xx.250 on the servers, defined to
   run on two or more of the NFS/GFS servers.
3. NFS mount the file system through the virtual IP on five
   NFS clients.  In my case, trin-12,13,14,15 and 16.
4. Run the genesis QE test case to create a directory for each
   client, and multiple files inside each.
5. While genesis is running, use the following script to move the
   virtual IP from node to node:

#!/bin/bash
for ((a=1; a>0; a++))
do
        clusvcadm -r xx.xx.xx.250 -m roth-02
        sleep 20
        clusvcadm -r xx.xx.xx.250 -m roth-01
        sleep 20
done
exit 0

Actual results:
Around 25 to 50% of the runs, the kernel will panic.

Expected results:
No kernel panic.

Additional info:
See call trace in the attachment for more information.

Also see bz #190756 for additional information.

I realize this is an awkward setup, so please contact me if you
want me to recreate this.  These are only my test clusters, so I can
put debug code on easily and let you have the machines to recreate
this.  Also, let me know if I can help in any way.
Comment 1 Robert Peterson 2007-01-05 17:33:24 EST
Created attachment 144941 [details]
Several instances of kernel panic from my test
Comment 3 Ric Wheeler 2010-03-16 13:26:08 EDT
Three year old issue - please reopen if this still occurs.

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