[Bugs] [Bug 1445189] New: Bug in stripe xlator makes write op never returned

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1445189

            Bug ID: 1445189
           Summary: Bug in stripe xlator makes write op never returned
           Product: GlusterFS
           Version: mainline
         Component: stripe
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: zhhuan at gmail.com
                CC: bugs at gluster.org



Description of problem:

There is a lock issue in the stripe xlator. It took the wrong lock for a frame
so that the call counter might not be updated correctly, making an fop never
returned.

This issue is easy to reproduce when gluster client is configured with more
than one event threads and request size is larger than stripe size. 

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


How reproducible:
Very often

Steps to Reproduce:
1. create a stripe volume
2. use fio to write to this volume, make sure block size larger than stripe
size

Actual results:
fio process hangs

Expected results:
fio finish test successfully

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.