Bug 1063190
Summary: | [RHEV-RHS] Volume was not accessible after server side quorum was met | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> |
Component: | replicate | Assignee: | Pranith Kumar K <pkarampu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | gluster-bugs, grajaiya, josh, kparthas, nlevinki, pkarampu, rcyriac, sasundar, sdharane, shaines, smanjara, tkatarki, vagarwal, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.5.1beta | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1061580 | Environment: |
virt rhev integration
|
Last Closed: | 2014-06-24 11:03:20 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: | 1061580 | ||
Bug Blocks: | 1062256 |
Comment 1
Anand Avati
2014-02-10 09:09:22 UTC
REVIEW: http://review.gluster.org/6944 (cluster/afr: Remove eager-lock stub on finodelk failure) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/6944 (cluster/afr: Remove eager-lock stub on finodelk failure) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/6944 committed in master by Anand Avati (avati) ------ commit e75be8977ede9b9174d20b39c427e6fb4ccde567 Author: Pranith Kumar K <pkarampu> Date: Mon Mar 24 22:54:03 2014 +0530 cluster/afr: Remove eager-lock stub on finodelk failure Problem: For write fops afr's transaction eager-lock init adds transactions that can share eager-lock to fdctx list. But if eager-lock finodelk fop fails the stub remains in the list. This could later lead to corruption of the list and lead to infinite loop on the list leading to a mount hang. Fix: Remove the stub when finodelk fails. Change-Id: I0ed4bc6b62f26c5e891c1181a6871ee6e4f4f5fd BUG: 1063190 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/6944 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Ravishankar N <ravishankar> Reviewed-by: Anand Avati <avati> REVIEW: http://review.gluster.org/7748 (cluster/afr: Remove eager-lock stub on finodelk failure) posted (#1) for review on release-3.5 by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/7748 committed in release-3.5 by Niels de Vos (ndevos) ------ commit 4b2da260afb962c3411e75cb450e081e675e51ff Author: Pranith Kumar K <pkarampu> Date: Tue May 13 14:49:47 2014 +0530 cluster/afr: Remove eager-lock stub on finodelk failure Problem: For write fops afr's transaction eager-lock init adds transactions that can share eager-lock to fdctx list. But if eager-lock finodelk fop fails the stub remains in the list. This could later lead to corruption of the list and lead to infinite loop on the list leading to a mount hang. Fix: Remove the stub when finodelk fails. Change-Id: Ic9d1368907c32edb4ea2e6db623e869e4f50180d BUG: 1063190 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/7748 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos> Tested-by: Niels de Vos <ndevos> The first (and last?) Beta for GlusterFS 3.5.1 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.1beta release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-May/040377.html [2] http://supercolony.gluster.org/pipermail/gluster-users/ 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.5.1, please reopen this bug report. glusterfs-3.5.1 has been announced on the Gluster Users mailinglist [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] http://supercolony.gluster.org/pipermail/gluster-users/2014-June/040723.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |