[Samba] 4.1.7 Server Side Copies & Disk Permissions
David Disseldorp
ddiss at suse.de
Wed Apr 30 03:07:47 MDT 2014
On Mon, 28 Apr 2014 18:01:10 +0200, steve wrote:
> > For the record, the issue is caused by Samba's setting of the
> > "vfs objects" parameter when running as an AD domain controller.
> >
> > https://bugzilla.samba.org/show_bug.cgi?id=10560
> >
> > If "vfs objects" is not set, then Samba configures the dfs_samba4 and
> > acl_xattr VFS modules. If it is set, then the parameter is left as is.
> >
> > Which means if a user goes from...
> >
> > [global]
> > server role = active directory domain controller
> > [share]
> > path = /samba/samba1/
> > read only = No
> >
> > to...
> >
> > [global]
> > server role = active directory domain controller
> > [share]
> > path = /samba/samba2/
> > read only = No
> > vfs objects = btrfs
> >
> > ...then the acl_xattr module is implicitly disabled, breaking the users
> > existing ACL<->xattr mapping setup.
> >
> > AFAICT, this behaviour is currently undocumented.
>
> Ah. So GPOs and using the DC as a file server for user shares won't work
> with btrfs? Or only until 10560 is solved?
No. This is not related to vfs_btrfs, it affects any VFS module. I'll
update the bug title to reflect this.
To workaround this behavior, you should check the testparm output for
preconfigured vfs modules prior to defining a "vfs objects" parameter.
Any desired vfs modules should then be defined alongside the previously
preconfigured modules.
Using Rowland's output as an example, if testparm shows
'vfs objects = dfs_samba4, acl_xattr' without any 'vfs objects'
definition in smb.conf, then to enable vfs_btrfs module, you should
explicitly define 'vfs objects = dfs_samba4, acl_xattr, btrfs'
As mentioned, this bug only affects configurations with
"server role = active directory domain controller".
Cheers, David
More information about the samba
mailing list