Advice for building samba-glusterfs-vfs

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

 



Correct, but I specifically don't want acl, xattr or user_xattr
enabled.  Standard u/g/o permissions is all our business requires.

The new patch mentioned earlier fixes my log-filling problem, which is
great!   Huge thanks for that submission.

-Dan


On 15 October 2013 17:39, Anand Avati <avati at gluster.org> wrote:
> Very likely reason for getting ENODATA for posix_acl_default key is because
> your backend is not mounted with -o acl?
>
> Avati
>
>
> On Mon, Oct 14, 2013 at 12:41 AM, Vijay Bellur <vbellur at redhat.com> wrote:
>>
>> On 10/11/2013 10:20 AM, Dan Mons wrote:
>>>
>>> Following up on this:
>>>
>>> * GlusterFS 3.4.1 solves the problem of renaming over CIFS from a
>>> Windows client (via Samba3 and vfs_glusterfs/libgfapi).  Happy days!
>>>
>>> * I still see 4 lines of this sort of thing for each file read in
>>> /var/log/glusterfs/bricks/*.log:
>>>
>>> "[2013-10-11 04:01:37.554826] E [posix.c:2668:posix_getxattr]
>>> 0-prodbackup-posix: getxattr failed on /gback_brick0/vfx:
>>> system.posix_acl_default (No data available)"
>>
>>
>> Have sent a patch to lower the severity of this log message to DEBUG when
>> the error number maps to "No data available":
>>
>> http://review.gluster.org/#/c/6084/
>>
>> -Vijay
>>
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>
>



-- 
Dan Mons
R&D SysAdmin
Cutting Edge
http://cuttingedge.com.au


[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