+++ This bug was initially created as a clone of Bug #1283032 +++ +++ This bug was initially created as a clone of Bug #1282747 +++ Description of problem: ============ While file is self healing append to the file hangs Version-Release number of selected component (if applicable): ========= glusterfs-server-3.7.5-6 How reproducible: Steps to Reproduce: ============= 1. Create 1x2 volume and mount it on client using fuse 2. Bring down one of the brick and create a big file 2 GB 3. Bring back the down brick and while self heal is going on try to append it to the file but it hangs untill self heal completes Actual results: Expected results: =========== Append to the file should complete without hangs
REVIEW: http://review.gluster.org/12653 (afr: Drop compatibility lock for data self-heal) posted (#1) for review on release-3.7 by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/12653 (afr: Drop compatibility lock for data self-heal) posted (#2) for review on release-3.7 by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/12653 (afr: Drop compatibility lock for data self-heal) posted (#3) for review on release-3.7 by Ravishankar N (ravishankar)
COMMIT: http://review.gluster.org/12653 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit f46a54326871bed28c64cd5312b250c7c8207e4f Author: Ravishankar N <ravishankar> Date: Wed Nov 18 08:30:48 2015 +0530 afr: Drop compatibility lock for data self-heal Backport of http://review.gluster.org/#/c/12602/ In glusterfs 3.4 and older, AFR did not take locks in self-heal domain during data self-heal. So this compat lock in data domain was added to prevent older clients from trying to heal a file while an existing self-heal was going on by a newer client. But the side effect was that all appending writes (which take full locks in data domain) from mounts would be stalled until self-heal was complete. Since glusterfs 3.4 is not supported anymore, remove the compat lock. Change-Id: I20bb2edf7527ce5d8291d13eb8b9149e66e9bcac BUG: 1283478 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/12653 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
v3.7.7 contains a fix.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.7, please open a new bug report. glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user