Created attachment 13922 [details] log.smbd [log.smb attached] $ uname -srv FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #13 5085b9023(trueos-master): Sat Dec 30 17:10:29 UTC 2017 root@chimera:/usr/obj/usr/src/amd64.amd64/sys/GENERIC $ env PYTHON=/usr/local/bin/python2.7 \ CC=gcc \ CFLAGS=-m64 \ CPPLAGS=-I/usr/local/include \ LDFLAGS="-m64 -R/opt/samba/lib -R/opt/samba/lib/private -R/usr/local/lib" \ ./configure --prefix=/opt/samba --sysconfdir=/etc/opt/samba \ --localstatedir=/var/opt/samba --enable-gnutls \ --with-privatedir=/var/opt/samba/private --with-ntvfs-fileserver \ --enable-avahi # cat smb.conf [global] workgroup = WORKGROUP netbios name = p150em log level = 10 passdb backend = tdbsam vfs objects = zfsacl [timecapsule] path = /foo/timecapsule writable = yes browsable = yes read only = no guest ok = no #create mask = 0666 #directory mask = 0755 fruit:time machine = yes
Created attachment 13923 [details] log.nmbd
I can provide truss and tcpdump if helpful. John groenveld@acm,org
Created attachment 13930 [details] log.smbd
Created attachment 13931 [details] log.smbd
Same Time Machine error with MacOS 10.13.3 and samba 4.8.0.rc2 John groenveld@acm.org
You need to load the `fruit' VFS module; this usually requires loading the `catia' and `streams_xattr' modules as well. See the vfs_fruit manpage for examples. In this case, you need to add `catia fruit streams_xattr` to your `vfs objects' line in smb.conf.
Just an update for the Time Machine time capsule users who stumble on this bug. Catia module is not required, setting this in [global] worked: vfs objects = fruit streams_xattr zfsacl John groenveld@acm.org