[Samba] vfs fruit unable to create xattr and ACL from OS X 10.10.4

[Ralph Böhme]

Hi Michal
On Fri, Jul 31, 2015 at 02:47:03PM +0200, Michal Moravec wrote:
> > On 29 Jul 2015, at 10:02, Ralph Böhme <rb at sernet.de> wrote:
> > Hm, works for me:
> > 
> > mac$ mount | grep smb
> > //ralph at 10.10.11.100 <mailto:ralph at 10.10.11.100>/AAPL on /Volumes/AAPL (smbfs, nodev, nosuid, mounted by ralph)
> > mac$ touch /Volumes/AAPL/test
> > mac$ xattr -w foo bar /Volumes/AAPL/test
> > mac$ xattr -l /Volumes/AAPL/test
> > foo: bar
> > mac$ 
> 
> 
> It does not matter if I use ls -la@ or xattr -l. Nothing is there.
> 
> > As expected, afair the client doesn't support modifyint ACLs on an smb
> > mount. Have you verified this works against an Apple SMB server?
> 
> I didn’t know that. I confirm client can’t do this with Apple SMB server either.
> Thank you for info.
> 
> 
> >>       fruit:nfs_aces = yes
> >>       fruit:veto_appledouble = yes
> > 
> > fwiw, I'd remove anything that is the default.
> 
> Are there any possible problems with this approach apart from convention/cleaner config?
> Our Samba admin prefers it this way.
> 
> 
> > man setfattr
> admin-apple # touch test.txt
> admin-apple # setfattr -n user.test -v test test.txt
> admin-apple # setfattr -n security.test -v test2 test.txt
> admin-apple # getfattr -d test.txt
> # file: test.txt
> user.test="test"
> 
> admin-apple # getfattr -n security.test -d test.txt
> # file: test.txt
> security.test="test2"
> 
> >From this output I conclude extended attributes are indeed supported on our storage array.
> 
> > I'd be happy to help, but being busy atm I'll have to see when to take
> > another look.
>
> Thank you. I would appriciate some tips how to debug this and find
> what is causing this problem.

please file a bugreport and attach a level 10 debug log.

-Ralph

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de,mailto:kontakt@sernet.de