REVIEW: http://review.gluster.org/7147 (extras/hookscripts: Add `%P` as default relative root) posted (#1) for review on master by Harshavardhana (harsha)
REVIEW: http://review.gluster.org/7147 (extras/hookscripts: Add `%P` as default relative root) posted (#2) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/7147 committed in master by Anand Avati (avati) ------ commit fc01b0293bef8ba14650c6a52f733bb6b6b77954 Author: Harshavardhana <harsha> Date: Fri Feb 21 12:45:48 2014 -0800 extras/hookscripts: Add `%P` as default relative root ctdb in its monitoring script looks for the "path" variable values at the system level not at share level. This relative root path, if any should be default for all volumes, to avoid issues with ctdb when doing subdirectory shares. Error: 2014/02/21 12:50:34.355754 [41083]: ERROR: samba directory "/foodir" not available Fix: Add %P in your smb.conf [gluster-foodir] ... ... path = %P/foodir ... ... Change-Id: If3c110d844ba8301c901dbce40b23cac99d6d55b BUG: 1068776 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/7147 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Jose A. Rivera <jarrpa> Reviewed-by: Anand Avati <avati>
REVIEW: http://review.gluster.org/7598 (extras/hookscripts: Remove %P from smb share path value.) posted (#1) for review on master by Raghavendra Talur (rtalur)
Posted patch http://review.gluster.org/7598 because %P option was restricting windows clients from being able to mount the sub directory shares. Solution to the original problem is to use the following config option. CTDB_SAMBA_SKIP_SHARE_CHECK=yes in ctdb.conf. This will stop ctdb from verifying the backend of shares.
COMMIT: http://review.gluster.org/7598 committed in master by Vijay Bellur (vbellur) ------ commit f48656b32e328f96bda5aade55070867d5faf333 Author: Raghavendra Talur <rtalur> Date: Tue Apr 29 14:28:29 2014 +0530 extras/hookscripts: Remove %P from smb share path value. We had added %P in the value for path in smb share definitions to avoid ctdb errors. However, %P does not work well for windows clients and they fail to access the share. Solution for the original problem: The error messages were being generated by a monitoring script that ctdb runs. The script reads the path value from testparm and tests if it exists in the local machine. This particular check does not hold valid for virtual file system backends like gluster. There is no harm in asking ctdb to not to check the existence of such backend and can be done by setting the following config in ctdb.conf: CTDB_SAMBA_SKIP_SHARE_CHECK=YES. Change-Id: I91627c8a279126a5cc24c6347847f9bfbad53dd5 BUG: 1068776 Signed-off-by: Raghavendra Talur <rtalur> Reviewed-on: http://review.gluster.org/7598 Reviewed-by: Jose A. Rivera <jarrpa> Reviewed-by: Poornima G <pgurusid> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Harshavardhana <harsha>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 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-September/018836.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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users