Bug 645563

Summary: GFS2: glock with no holder
Product: Red Hat Enterprise Linux 5 Reporter: Anton Mark <amark>
Component: kernelAssignee: Robert Peterson <rpeterso>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.5.zCC: bturner, rpeterso
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 15:45:42 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
gfs2_hangalyzer output showing lost locks none

Description Anton Mark 2010-10-21 20:25:45 UTC
Created attachment 454927 [details]
gfs2_hangalyzer output showing lost locks

Description of problem:
Customer reported GFS2 IO freeze.  Running gfs2_hangalyzer reports pid waiting for glock but no holder found.

Version-Release number of selected component (if applicable):
RHEL 5.5.z

How reproducible:
Customer generally ran in to this problem once a week.

Steps to Reproduce:
Details are not known yet exactly how to make it happen.  It seems to have to do with active/active mail server workload.

Actual results:
All IO on a specific GFS2 file system would eventually stop (or at least appear to stop).

Expected results:
IO doesn't stop.

Additional info:
Will attach gfs2_hangalyzer output with missing locks.  Gave customer 2.6.18-209.el5.x86_64.rpm test kernel and this appears to have fixed the lost locks part of this.

Comment 1 Robert Peterson 2010-11-08 17:45:05 UTC
This may be a duplicate of bug #595397.

Comment 2 Ben Turner 2010-11-10 15:45:42 UTC

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