Bug 616504 - Problem with reboot/halt of a cluster node
Summary: Problem with reboot/halt of a cluster node
Keywords:
Status: CLOSED DUPLICATE of bug 609075
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.5
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-20 15:52 UTC by rauch
Modified: 2011-01-26 14:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-26 14:57:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
messages (6.60 KB, application/octet-stream)
2010-07-20 15:52 UTC, rauch 		no flags Details
cluster.conf (2.50 KB, text/plain)
2010-07-20 15:54 UTC, rauch 		no flags Details
View All

Description rauch 2010-07-20 15:52:59 UTC 
Created attachment 433200 [details]
messages

Description of problem:

It is not possible to reboot/halt a cluster node without a gfs filesystem freeze for several seconds (~30) and a fence of the node.


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

RHEL 5.5 latest updates
cman-2.0.115-34.el5_5.1
kernel-2.6.18-194.8.1.el5
openais-0.80.6-16.el5_5.2
kmod-gfs-0.1.34-12.el5
gfs-utils-0.1.20-7.el5

How reproducible:

Instal RHEL 5.5 with latest updates and setup a cluster and reboot one node.


Steps to Reproduce:
1. Setup a 2 node cluster with qdisk
2. Reboot a node
3. try read/write from/to the gfs filesystem
  
Actual results:
The cluster filesystem (gfs) freeze for several seconds (~30) and the node gets fenced

Expected results:
Stopping a cluster node should not result in a filesystem freeze and a fence of the node.

Additional info:
Attached cluster.conf and messages
Comment 1 rauch 2010-07-20 15:54:12 UTC 
Created attachment 433202 [details]
cluster.conf

cluster.conf
Comment 2 Lon Hohberger 2011-01-26 14:57:52 UTC 

*** This bug has been marked as a duplicate of bug 609075 ***
Note You need to log in before you can comment on or make changes to this bug.