Description of problem: Often, multiple io-threads could be attempting to create a shard at the same time, causing one of those attempts to fail with EEXIST. This is being logged at ERROR level today. It can be suppressed by moving it to DEBUG. See http://www.gluster.org/pipermail/gluster-users/2016-August/028039.html for more information. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15161 (storage/posix: Log EEXIST failures at DEBUG log-level) posted (#1) for review on master by Krutika Dhananjay (kdhananj)
COMMIT: http://review.gluster.org/15161 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 020c39e8ab657fbf12c102186c14aca24239efd4 Author: Krutika Dhananjay <kdhananj> Date: Tue Aug 16 10:43:07 2016 +0530 storage/posix: Log EEXIST failures at DEBUG log-level Change-Id: I56f160058d2e2751ca75f1f75ea8254a1b8a6bf3 BUG: 1367258 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: http://review.gluster.org/15161 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.0, please open a new bug report. glusterfs-3.9.0 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/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/