Description of problem: 2 replica volume. Enabled both geo-replication and quota. Kept untar and building of glusterfs on the fuse mount. Added one more brick to the volume and thus increased the replica count to 3.(did not enter the gluster heal command after add-brick). glusterfs build hung with blocked entrylks. Had done stat-prefetch off/on Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create a replicate volume, start gsync and quota on the volume 2. Keep glusterfs untar and compilation on mount point 3. Do add brick to the volume thus increasing the replica count Actual results: Expected results: Additional info: new Type: Replicate Volume ID: 75160aa1-3053-44cb-973f-7fb0d63a93d3 Status: Started Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: hyperspace:/mnt/sda7/export3 Brick2: hyperspace:/mnt/sda8/export3 Brick3: hyperspace:/mnt/sda10/export3 Options Reconfigured: performance.stat-prefetch: on features.quota: on geo-replication.indexing: on
Created attachment 585625 [details] client statedump file
Created attachment 585626 [details] brick statedump file
Created attachment 585629 [details] client log file
Created attachment 585640 [details] log file of the client process started by geo-replication
I am not sure, why bz is not updated with the following commit bb2fc0a23e46413a14baef1846a9873681d32fe2 This bug is fixed.
Checked with release-3.3 branch (git head: 638a4740cc553c96bc01d1dfe4a2b7acf0b406e6) and did not find any blocked entrylks.