Description of problem: when we create a volume, the default volume file will add the default options in the glusterd's volume set tables, as several options is obsolete, the brick's log will complain like "_log_if_unknown_option] 0-patchy-quota: option 'timeout' is not recognized" 143 123: volume patchy-quota 144 124: type features/quota 145 125: option volume-uuid patchy 146 126: option server-quota off 147 127: option timeout 0 //this option is obsolete 148 128: option deem-statfs off 149 129: subvolumes patchy-index 150 130: end-volume Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/17213 (glusterd: remove useless options from glusterd's volume set table) posted (#1) for review on master by Zhou Zhengping (johnzzpcrystal)
REVIEW: https://review.gluster.org/17213 (glusterd: remove useless options from glusterd's volume set table) posted (#2) for review on master by Zhou Zhengping (johnzzpcrystal)
REVIEW: https://review.gluster.org/17213 (glusterd: remove useless options from glusterd's volume set table) posted (#3) for review on master by Zhou Zhengping (johnzzpcrystal)
COMMIT: https://review.gluster.org/17213 committed in master by Jeff Darcy (jeff.us) ------ commit be14d189360d09f8e10e6b75326df6d1db306467 Author: Zhou Zhengping <johnzzpcrystal> Date: Tue May 9 12:13:37 2017 +0800 glusterd: remove useless options from glusterd's volume set table These options will cause brick's log complains: _log_if_unknown_option] 0-patchy-quota: option 'timeout' is not recognized _log_if_unknown_option] 0-patchy-server: option 'ping-timeout' is not recognized Change-Id: Ida2add13f792736a4e52bfaf38d1169309283a3f BUG: 1449008 Signed-off-by: Zhou Zhengping <johnzzpcrystal> Reviewed-on: https://review.gluster.org/17213 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Prashanth Pai <ppai> Reviewed-by: Jeff Darcy <jeff.us>
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.12.0, please open a new bug report. glusterfs-3.12.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-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/