[Samba] 4.1.7 Server Side Copies & Disk Permissions

[David Disseldorp]

On Mon, 28 Apr 2014 19:50:02 +0100, Stuart Naylor wrote:

> If you want to use extended server side copies, which are pretty neat then actually no copy happens just the btrfs metadata is changed.
> 
> So firstly with no change with btrfs or ext4 or ... server side copies work.
> 
> For extended server side copies to use all the niceness of btrfs the vfs objects =  btrfs needs to be set.

Stay tuned for 4.2, where you'll get transparent compression support
too :-)
http://blog.elastocloud.org/2014/01/samba-transparent-file-compression-on.html

> Then I had loads of problems with permissions.
> 
> This is because the defaults are turned off when you supply vfs objects = btrfs (or any vfs object)
> So it needs to be slightly more to bring back in the defaults vfs objects = dfs_samba4, acl_xattr, btrfs

Yes exactly, keeping in mind that this only occurs when configured as an
AD DC (server role = active directory domain controller).

In fixing this, I'm evaluating the following options:

1. Print a loud warning in the log (and possibly fail to start) when
   an AD DC configured server includes an explicit "vfs objects"
   definition that does not include the modules that it requires
   (dfs_samba4, acl_xattr).
2. Append the required vfs modules to any explicit "vfs objects"
   definition, filtering out duplicates.

I'm leaning towards (1) ATM, as I don't like the idea of magically
changing what has been defined by the user - that's what got us into
this mess in the first place.
Anyhow, I'm open to other suggestions.

Cheers, David