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:
Created attachment 1273851 [details] patch file to fix this issue I don't know why I got notified that I don't have permission to submit this patch. I also notice that I don't permission to sign into review.gluster.org with my github account. Therefore I attach the patch of this fix here. Hope it would help.
Stripe xlator is deprecated. Use the shard option instead.