Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1696599

Summary: Fops hang when inodelk fails on the first fop
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: replicateAssignee: bugs <bugs>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1699731 (view as bug list) Environment:
Last Closed: 2019-04-15 06:03:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1688395, 1699731, 1699736    

Description Pranith Kumar K 2019-04-05 08:35:03 UTC 
Description of problem:
Steps:
glusterd

gluster peer probe localhost.localdomain
peer probe: success. Probe on localhost not needed
gluster --mode=script --wignore volume create r3 replica 3 localhost.localdomain:/home/gfs/r3_0 localhost.localdomain:/home/gfs/r3_1 localhost.localdomain:/home/gfs/r3_2
volume create: r3: success: please start the volume to access data
gluster --mode=script volume start r3
volume start: r3: success
mkdir: cannot create directory ‘/mnt/r3’: File exists

mount -t glusterfs localhost.localdomain:/r3 /mnt/r3

First terminal:
# cd /mnt/r3
# touch abc
Attach the mount process in gdb and put a break point on function afr_lock()
From second terminal:
# exec 200>abc
# echo abc >&200
# When the break point is hit, on third terminal execute "gluster volume stop r3"
# quit gdb
# execute "gluster volume start r3 force"
# On the first terminal execute "exec abc >&200" again and this command hangs.


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


How reproducible:
Always

Actual results:


Expected results:


Additional info:
Comment 1 Worker Ant 2019-04-05 08:37:54 UTC 
REVIEW: https://review.gluster.org/22515 (cluster/afr: Remove local from owners_list on failure of lock-acquisition) posted (#1) for review on master by Pranith Kumar Karampuri
Comment 2 Worker Ant 2019-04-15 06:03:00 UTC 
REVIEW: https://review.gluster.org/22515 (cluster/afr: Remove local from owners_list on failure of lock-acquisition) merged (#6) on master by Pranith Kumar Karampuri