[Gluster-users] Strange problem using samba_vfs_gluster

[Daniel Müller]

glusterfs:volume= yourmountedglustervol
glusterfs:volfile_server = 172.17.1.1 <--simetimes needed the ip

Good Luck
Daniel

EDV Daniel Müller


EDV Daniel Müller

Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 Tübingen 
Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mueller at tropenklinik.de
Internet: www.tropenklinik.de





-----Ursprüngliche Nachricht-----
Von: gluster-users-bounces at gluster.org
[mailto:gluster-users-bounces at gluster.org] Im Auftrag von Lalatendu Mohanty
Gesendet: Freitag, 27. Juni 2014 06:45
An: Michael DePaulo; Volnei
Cc: gluster-users at gluster.org
Betreff: Re: [Gluster-users] Strange problem using samba_vfs_gluster

On 06/27/2014 06:04 AM, Michael DePaulo wrote:
> On Thu, Jun 26, 2014 at 8:20 AM, Volnei <volnei at vcplinux.com.br> wrote:
>> Hi,
>>
>> If I use the configuration method "vfs" I can see the share, But I 
>> cannot write anything into it.
>> On Windows7, for example, the following message is showed:
>>
>> Error 0x8007045D: the request could not be performed because of an 
>> I/O device error ever I try create a folder or a file.
>>
>> If I use the configuration at mount point, then everything works
perfectly.
>>
>> This is a bug or I'm doing something wrong.
>>
>> Thanks a lot
>>
>> (smb.conf)
>>
>> [GV0-GLUSTERFS]
>>          comment = For samba share of volume gv0
>>          path = /
>>          writable = Yes
>>          read only = No
>>          guest ok = Yes
>>          browseable = yes
>>          create mask = 0777
>>          kernel share modes = No
>>          vfs objects = glusterfs
>>          glusterfs:loglevel = 7
>>          glusterfs:logfile = /var/log/samba/glusterfs-testvol.log
>>          glusterfs:volume = gv0
>>
>> # This works fine
>> #[GLUSTERFS_DATAS]
>> #        comment = glusterfs via mountpoint
>> #        path = /mnt/dados
>> #        writable = Yes
>> #        guest ok = Yes
>> #        browseable = yes
>> #        create mask = 0777
>>
>>
>> Erro message when I use vfs_gluster
>>
>> [2014-06-26 12:06:57.293530] E
>> [afr-self-heal-common.c:233:afr_sh_print_split_brain_log]
0-gv0-replicate-0:
>> Unable to self-heal contents of '/.' (possible split-brain). Please 
>> delete the file from all but the preferred subvolume.- Pending 
>> matrix:  [ [ 0 2 ] [
>> 2 0 ] ]
>> [2014-06-26 12:06:57.294679] E
>> [afr-self-heal-common.c:2859:afr_log_self_heal_completion_status]
>> 0-gv0-replicate-0:  metadata self heal  failed,   on /.
>>
>>
>>
>> Versions:
>>
>> samba-4.1.9-3.fc20.x86_64
>> samba-vfs-glusterfs-4.1.9-3.fc20.x86_64
>> samba-common-4.1.9-3.fc20.x86_64
>> samba-winbind-4.1.9-3.fc20.x86_64
>> samba-winbind-clients-4.1.9-3.fc20.x86_64
>> samba-libs-4.1.9-3.fc20.x86_64
>> samba-winbind-modules-4.1.9-3.fc20.x86_64
>> samba-winbind-krb5-locator-4.1.9-3.fc20.x86_64
>> samba-client-4.1.9-3.fc20.x86_64
>>
>> glusterfs-fuse-3.5.0-3.fc20.x86_64
>> glusterfs-server-3.5.0-3.fc20.x86_64
>> glusterfs-libs-3.5.0-3.fc20.x86_64
>> glusterfs-api-3.5.0-3.fc20.x86_64
>> glusterfs-cli-3.5.0-3.fc20.x86_64
>> glusterfs-3.5.0-3.fc20.x86_64
>>
> On a related note, has anyone had success using samba_vfs_gluster with 
> glusterfs 3.5.x instead of 3.4.x? Is it even supported?
>
> The example post uses 3.4.x:
> http://lalatendumohanty.wordpress.com/2014/02/11/using-glusterfs-with-
> samba-and-samba-vfs-plugin-for-glusterfs-on-fedora-20/
> _______________________________________________
>
I think I had tested early versions of glusterfs 3.5.0 with samba vfs plugin
and it had worked fine. It should work as mentioned in the above blog post.
If it is not working, then it might be a genuine bug or configuration issue.

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