SOLVED Impossible to mount SMB share after 11.2 > 11.3 upgrade

gregober

Dabbler
Joined
Sep 30, 2012
Messages
17
I have a SMB share setup since ages and have been upgraded my FreeNAS server on regular basis.
I am using Mac OS X 10.15

The 11.2 >> 11.3 upgrade seems preety obvious.
I first upgraded to the latest 11.2 release and then move on to the the new branch 11.3 which seems quite straightforward.

Since then, I am unable to use my SMB share.
I have tried to update some settings, but most of them were quite straightforward (and worked before with 11.2).

The log seems to indicate that there is a missing file "dfs_samba4.so":

Feb 19 12:55:56 sand smbd[11970]: [2020/02/19 12:55:56.224084, 0] ../../source3/smbd/vfs.c:185(vfs_init_custom)
Feb 19 12:55:56 sand smbd[11970]: error probing vfs module 'dfs_samba4': NT_STATUS_UNSUCCESSFUL
Feb 19 12:55:56 sand smbd[11970]: [2020/02/19 12:55:56.224170, 0] ../../source3/smbd/vfs.c:380(smbd_vfs_init)
Feb 19 12:55:56 sand smbd[11970]: smbd_vfs_init: vfs_init_custom failed for dfs_samba4
Feb 19 12:55:56 sand smbd[11970]: [2020/02/19 12:55:56.224249, 0] ../../source3/smbd/service.c:633(make_connection_snum)
Feb 19 12:55:56 sand smbd[11970]: make_connection_snum: vfs_init failed for service Private-PC
Feb 19 12:55:56 sand smbd[11970]: [2020/02/19 12:55:56.225155, 0] ../../lib/util/modules.c:49(load_module)
Feb 19 12:55:56 sand smbd[11970]: Error loading module '/usr/local/lib/shared-modules/vfs/dfs_samba4.so': Cannot open "/usr/local/lib/shared-modules/vfs/dfs_samba4.so"

If I try to list what's inside this directory : /usr/local/lib/shared-modules/vfs/
I have no trace of the dfs_samba4.so
[root@sand /mnt/tank/Home/gregober]# ls /usr/local/lib/shared-modules/vfs/
acl_tdb.so fake_perms.so shell_snap.so
acl_xattr.so fruit.so streams_depot.so
aio_fbsd.so full_audit.so streams_xattr.so
aio_fork.so ixnas.so syncops.so
aio_pthread.so linux_xfs_sgid.so time_audit.so
aio_spthread.so media_harmony.so tmprotect.so
audit.so netatalk.so unityed_media.so
cacheprime.so noacl.so virusfilter.so
cap.so offline.so winmsa.so
catia.so preopen.so worm.so
commit.so readahead.so xattr_tdb.so
crossrename.so readonly.so zfs_fsrvp.so
default_quota.so recycle.so zfs_space.so
dirsort.so shadow_copy_zfs.so zfsacl.so
expand_msdfs.so shadow_copy.so
extd_audit.so shadow_copy2.so


There is no trace on the system of the dfs_samba4.so anywhere
So I don't really know what to do…
 
Last edited:
Joined
Jul 2, 2019
Messages
648

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Code:
bld.SAMBA3_MODULE('vfs_dfs_samba4',
                 subsystem='vfs',
                 source='vfs_dfs_samba4.c',
                 deps='samba-util dfs_server_ad samdb tevent',
                 init_function='',
                 internal_module=bld.SAMBA3_IS_STATIC_MODULE('vfs_dfs_samba4') and bld.AD_DC_BUILD_IS_ENABLED(),
                 enabled=bld.SAMBA3_IS_ENABLED_MODULE('vfs_dfs_samba4') and bld.AD_DC_BUILD_IS_ENABLED())

vfs_dfs_samba4 is only built if samba is compiled with AD DC support. Can you remove the VFS module from your share and test whether the functionality works without it.
 

gregober

Dabbler
Joined
Sep 30, 2012
Messages
17
After pulling my hair for couple of hours, I have finally found a bypass that solves the problem.

If you disable "streams_xattr" in the "VFS Objects" pannel then It solves your issue.
On Mac OS X 10.15 this seems to be the way to go.

I don't think this will be missed because "Enable storing NTFS alternate data streams in the file system. Enabled by default." is not used in our case.
Maybe others willing to share files between Win$ and Mac will be more impacted…

Good luck if you are in such case !
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
After pulling my hair for couple of hours, I have finally found a bypass that solves the problem.

If you disable "streams_xattr" in the "VFS Objects" pannel then It solves your issue.
On Mac OS X 10.15 this seems to be the way to go.

I don't think this will be missed because "Enable storing NTFS alternate data streams in the file system. Enabled by default." is not used in our case.
Maybe others willing to share files between Win$ and Mac will be more impacted…

Good luck if you are in such case !
What do you mean? Macs store metadata in alternate datastreams. If you turn off this functionality then the Mac clients will write this metadata to files.
 

gregober

Dabbler
Joined
Sep 30, 2012
Messages
17
What do you mean? Macs store metadata in alternate datastreams. If you turn off this functionality then the Mac clients will write this metadata to files.

I am not an expert in SMB share.
In my case I have tried to fix an issue which was that my mount point weren't available after the upgrade (couldn't mount my two SMB shares).

Disabling the "streams_xattr" solved the issue.
 

gregober

Dabbler
Joined
Sep 30, 2012
Messages
17
FYI: I have re-enabled it afterward and service seems to still be up and running.
 
Top