Re: Samba-VFS-Glusterfs issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/21/2014 02:33 PM, Jon Archer wrote:
Hi Lala,

Thanks for your response (here and on your blog), I did try removing the valid users statement but still no luck. Although I would imagine the valid users statement should work, otherwise how would we control access.

Jon

Jon,

Are you still facing this issue? if yes, can you please send us the output of "testparm -s" where your Samba server is running.



On 2014-07-18 10:59, Lalatendu Mohanty wrote:
On 07/17/2014 07:11 PM, Jon Archer wrote:
Hi all,

I'm currently testing out the samba-vfs-glusterfs configuration to look into replacing fuse mounted volumes.

I've got a server configured as per:
http://lalatendumohanty.wordpress.com/2014/02/11/using-glusterfs-with-samba-and-samba-vfs-plugin-for-glusterfs-on-fedora-20/ but am seeing an issue:
"Failed to set volfile_server..."

I have a gluster volume share:

Volume Name: share
Type: Replicate
Volume ID: 06d1eb42-873d-43fe-ae94-562e975cca9a
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: storenode1:/gluster/bricks/share/brick1
Brick2: storenode2:/gluster/bricks/share/brick1
Options Reconfigured:
server.allow-insecure: on


and this is then added as a share in samba:
[share]
comment = Gluster and CTDB based share
path = /
read only = no
guest ok = yes
valid users = jon
vfs objects = glusterfs
glusterfs:loglevel = 10
glusterfs:volume = share


The share is visible at top level just not accessible, if i do try to access it I get a samba client log entry of: [2014/07/17 13:31:56.084620, 0] ../source3/modules/vfs_glusterfs.c:253(vfs_gluster_connect)
Failed to set volfile_server localhost


I've tried setting the glusterfs:volfile_server option in smb.conf to IP, localhost and hostname with the same response just specifying IP,localhost or hostname in the error message.

Packages installed are:

rpm -qa|grep gluster
glusterfs-libs-3.5.1-1.el6.x86_64
glusterfs-cli-3.5.1-1.el6.x86_64
glusterfs-server-3.5.1-1.el6.x86_64
glusterfs-3.5.1-1.el6.x86_64
glusterfs-fuse-3.5.1-1.el6.x86_64
samba-vfs-glusterfs-4.1.9-2.el6.x86_64
glusterfs-api-3.5.1-1.el6.x86_64

rpm -qa|grep samba
samba-4.1.9-2.el6.x86_64
samba-common-4.1.9-2.el6.x86_64
samba-winbind-modules-4.1.9-2.el6.x86_64
samba-vfs-glusterfs-4.1.9-2.el6.x86_64
samba-winbind-clients-4.1.9-2.el6.x86_64
samba-libs-4.1.9-2.el6.x86_64
samba-winbind-4.1.9-2.el6.x86_64
samba-client-4.1.9-2.el6.x86_64


for purposes of testing I have disabled SELINUX and flushed all firewall rules.

Does anyone have any ideas on this error and how to resolve?

Hey Jon,

The output of "testparm -s" might help. Also you can try following

1. Remove the line "valid users = jon" from smb.conf
2. Set smbpasswd for root.
    $smbpasswd -a root

And try to access the share from the client (use root and <smbpasswd>)

-Lala
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux