Bug 1396780
Summary: | Make debugging EACCES errors easier to debug | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> |
Component: | posix-acl | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9 | CC: | bugs, hgowtham |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1394548 | Environment: | |
Last Closed: | 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: | 1394548 | ||
Bug Blocks: |
Description
Pranith Kumar K
2016-11-20 05:40:42 UTC
REVIEW: http://review.gluster.org/15886 (protocol/server: Print error-xlator name) posted (#1) for review on release-3.9 by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/15887 (protocol/server: Print pargfid in logs for rename error) posted (#2) for review on release-3.9 by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/15886 (protocol/server: Print error-xlator name) posted (#2) for review on release-3.9 by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/16058 (protocol/server: Remove unused variable) posted (#1) for review on release-3.9 by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/15887 committed in release-3.9 by Raghavendra Talur (rtalur) ------ commit 4b52890f52978231e0ccbcc2a4461683c7ca4b78 Author: Pranith Kumar K <pkarampu> Date: Thu Nov 17 21:02:29 2016 +0530 protocol/server: Print pargfid in logs for rename error Backport of http://review.gluster.org/15872 >BUG: 1394548 >Change-Id: I42ee627c8cdf54158f083f9019a096ace449e3cc >Signed-off-by: Pranith Kumar K <pkarampu> BUG: 1396780 Change-Id: I80c3d3c7994982b812857c6705b3bf4716bf0824 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/15887 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra Talur <rtalur> COMMIT: http://review.gluster.org/15886 committed in release-3.9 by Raghavendra Talur (rtalur) ------ commit 114537a2e11b3811dbf4f1ca0d4fd74d0c0b23c3 Author: Pranith Kumar K <pkarampu> Date: Sat Nov 12 16:47:00 2016 +0530 protocol/server: Print error-xlator name Problem: At the moment from which xlator the errors are stemming from is a mystery. Fix: With this patch we can find on the server side which xlator first gave the errno received by server xlator. I am not yet sure how to get this done for client side which has lot of copy_frame()s. May be another patch. >Change-Id: Ie13307b965facf2a496123e81ce0bd6756f98ac9 >BUG: 1394548 >Signed-off-by: Pranith Kumar K <pkarampu> >Reviewed-on: http://review.gluster.org/15836 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >Reviewed-by: Vijay Bellur <vbellur> >CentOS-regression: Gluster Build System <jenkins.org> BUG: 1396780 Change-Id: I3b293d21528da391eafd0fbaa5b451a1d3ddc237 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/15886 CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra Talur <rtalur> COMMIT: http://review.gluster.org/16058 committed in release-3.9 by Pranith Kumar Karampuri (pkarampu) ------ commit 670fe5633d6d80db380c2916613c457b4522c454 Author: Anoop C S <anoopcs> Date: Tue Nov 22 06:34:35 2016 +0000 protocol/server: Remove unused variable >Change-Id: I0d0a786b2d02d4db37c4da6194ee4b4feac31b63 >BUG: 1198849 >Signed-off-by: Anoop C S <anoopcs> >Reviewed-on: http://review.gluster.org/15899 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: Vijay Bellur <vbellur> BUG: 1396780 Change-Id: I78cb34d0f91c2f375c2e4e413337253b34987baa Signed-off-by: Anoop C S <anoopcs> Reviewed-on: http://review.gluster.org/16058 Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> 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.9.1, please open a new bug report. glusterfs-3.9.1 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] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.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.9.1, please open a new bug report. glusterfs-3.9.1 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] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.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.9.1, please open a new bug report. glusterfs-3.9.1 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] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |