Bug 162014

Summary:	gfs mounts allowed before fencing completes
Product:	[Retired] Red Hat Cluster Suite	Reporter:	David Teigland <teigland>
Component:	cman	Assignee:	David Teigland <teigland>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	cluster-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-734	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-07 16:46:44 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:

Description David Teigland 2005-06-29 04:11:54 UTC

Description of problem:
There is a corner case not handled by SM which can
result in new gfs mounts happening before a fencing
is completed for a failed node that had the fs mounted.
There is a chance of this leading to fs corruption.

- Nodes A, B, C are cluster members and all have joined
  the fence domain.

- A has gfs mounted, B and C do not.

- A fails.

- B and C begin fencing A.  This can take some time,
  especially noticable when using fence_manual.

- B and/or C mount gfs.

- The new mount by B/C is allowed to go ahead before
  the fencing for A has completed.

- If A is still writing to gfs and fencing has not
  completed before B/C do initial gfs recovery, the
  fs can be corrupted.

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

How reproducible:

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Expected results:

Additional info:

Comment 1 David Teigland 2005-06-30 05:30:00 UTC

Fixed in STABLE and RHEL4 branches:
SM should wait for all recoveries to complete before it processes
any group joins/leaves.  Fixes bz 162014.

Comment 3 Red Hat Bugzilla 2005-10-07 16:46:44 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-734.html