+++ This bug was initially created as a clone of Bug #1395745 +++ BR_STUB_QUARANTINE_DIR's definition uses a misspelling of quarantine, "quanrantine". A fix for this should include a method for renaming the misspelled directory on upgrade that will work for every distro. --- Additional comment from Worker Ant on 2016-12-02 16:16:32 EST --- REVIEW: http://review.gluster.org/16019 (features/bit-rot-stub: use the correct spelling of quarantine for bad objects container) posted (#1) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/16027 (features/bit-rot-stub: use the correct spelling of quarantine for bad objects container) posted (#1) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: http://review.gluster.org/16027 (features/bit-rot-stub: use the correct spelling of quarantine for bad objects container) posted (#2) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: https://review.gluster.org/16027 (features/bit-rot-stub: use the correct spelling of quarantine for bad objects container) posted (#3) for review on master by Raghavendra Bhat (raghavendra)
REVIEW: https://review.gluster.org/16027 (features/bit-rot-stub: use the correct spelling of quarantine for bad objects container) posted (#4) for review on master by Raghavendra Bhat (raghavendra)
COMMIT: https://review.gluster.org/16027 committed in master by Jeff Darcy (jdarcy) ------ commit 2e0dceb6165d0a93581284fa2e0d74abe4ee615b Author: Raghavendra Bhat <raghavendra> Date: Fri Dec 2 15:24:46 2016 -0500 features/bit-rot-stub: use the correct spelling of quarantine for bad objects container The directory for containing the list of bad objects was named "quanrantine" instead of "quarantine" Change-Id: I8c20381ac637201d9d1a224f5223e8dfbed53f1e BUG: 1401571 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: https://review.gluster.org/16027 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat>
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.11.0, please open a new bug report. glusterfs-3.11.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/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/