Bug 1268092
Summary: | samba-vfs-glusterfs share problems | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Steve D <sdainard> |
Component: | gluster-smb | Assignee: | Michael Adam <madam> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.6 | CC: | bugs, madam, rjoseph, sdainard |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-23 12:50:53 UTC | 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: |
Description
Steve D
2015-10-01 19:36:09 UTC
I would need more info: - full Samba configuration (all files, our output of 'testparm') - log files of samba, especially also the vfs-gluster log Could you also repeat the test on a vfs-glusterfs share without the 'force group' and 'write list' options? Just to check whether these are related. I was missing "kernel share modes = No" under the share definition. I think the biggest hurdle is hard to find documentation. Someone on the mailing list helped me out with this, but it should be easy to find. With a Google search I can find the info in a couple blog posts(1)(2), but not in the Gluster docs. Can you change this bug to a documentation bug so this gets fixed? 1. http://jonarcher.info/2014/09/gluster-cifs-zfs-kind-part-2/ 2. https://lalatendumohanty.wordpress.com/2014/02/11/using-glusterfs-with-samba-and-samba-vfs-plugin-for-glusterfs-on-fedora-20/ Recent versions of the vfs_glusterfs manual page have that documented: https://www.mankier.com/8/vfs_glusterfs It has also been brought to Samba 4.1 and 4.2: https://bugzilla.samba.org/show_bug.cgi?id=11117 Does that help? This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. If you still face this bug with the newer GlusterFS versions, please open a new bug. |