After upgrade to 4.4-6 errata767. a share on a Fileserver (memberserver) is not accesible
the old setting on the PDC was
this results in a (testpram -s)
vfs objects = acl_xattr "recycle streams_xattr shadow_copy2"
and so samba cannot load the vfs module
and the logfile shows
Error loading module ‘/usr/lib/x86_64-linux-gnu/samba/vfs/recycle streams_xattr shadow_copy2.so’: /usr/lib/x86_64-linux-gnu/samba/vfs/recycle streams_xattr shadow_copy2.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
[2020/10/16 08:58:28.431517, 0] …/…/source3/smbd/vfs.c:185(vfs_init_custom)
error probing vfs module ‘recycle streams_xattr shadow_copy2’: NT_STATUS_UNSUCCESSFUL
[2020/10/16 08:58:28.431559, 0] …/…/source3/smbd/vfs.c:380(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for recycle streams_xattr shadow_copy2
A change to comma instead of blank
recycle,streams_xattr,shadow_copy2
in the GUI applies now the attributes in a correct way (regarding to testparam)
[toffice]
csc policy = documents
dos filemode = Yes
hide unreadable = Yes
include = /etc/samba/local.conf
inherit acls = Yes
inherit owner = windows and unix
inherit permissions = Yes
map acl inherit = Yes
path = /mnt/tmoffice
read only = No
vfs objects = acl_xattr recycle streams_xattr shadow_copy2
recycle:noversions = *.tmp,*.temp,*.o,*.obj,*.TMP,*.TEMP
recycle:directory_mode = 0777
recycle:touch = YES
recycle:repository = .recycle/%U
recycle:keeptree = YES
recycle:versions = YES
recycle:subdir_mode = 0700
after a service samba reload the share is accessible again
So it seems the behavoir from older 4.3 upwards has now changed to use commas instead of blanks?
This is written to help others…
Rgds Lucky
Hi
I can confirm that this workaround has worked for me as well. I’ve been in touch with Univention support and since I’ve discovered your post in the midst of downgrading back to the last Samba package version. I can confirm that adding commas was the right thing to do and fixes the problematic shares on the latest errata level.
I’ve called Univention after validating my findings and referenced your thread. The’ll be working on a KB article. Since my system was updated to 4.4-6 recently and only updated to the latest Samba update this week I’m pretty certain that the iregression came up with this week’s errata updates.
TBH: I would have taken such a regression with more kindness if it had happened during a point release or a major upgrade, but not as a errata patch update.