Big Sur + SMB + Thunderbolt 3 - Finder Crash

Question

Created Nov ’20

Replies 4

Boosts 0

Views 1.7k

Participants 2

I use Samba 4.11.6 with ubuntu 20.04 & Mac os Big Sur 11.0.1.
I connected my macbook and server (intel nuc) via thunderbolt 3. It works fast, speeds around 800MB/s. I can easily transfer multiple files or 1 large file, but when I try to transfer any web project with a lot of files and subfolders, the finder freezes and only hard reset helps. I tried transferring files via finder and via cp -av ..., the result is the same - the terminal freezes and control + c does not work. Several files with a total size of a couple of KB are transferred and nothing else.

The problem is similar to this jamf.com/jamf-nation/discussions/26464/macos-high-sierra-10-13-2-finder-issues-when-copying-files-in-mounted-shares.

I tried changing nsmb.conf to this

Code Block [default]
signing_required=no
dir_cache_off=yes

But it didn't help at all :(

When I don't connect via thunderbolt 3, but when i connected via wifi, I can transfer my project to the smb folder.

Boost

Answer 1

Ben--- OP

Dec ’20

Hi OneNice,

I have an identical issue and I can reproduce it on multiple MacBook Pro running the latest Mojave, Catalina and Big Sur. I can consistently reproduce the issue with a CalDigit TS3+ or Belkin USB-C to Gigabit Ethernet Adapter. On Wi-Fi it works although I'm seeing other issues on Wi-Fi with a SMB mount.

I'm engaged with Apple Support but so far they aren't sure.

0

Answer 2

Ben--- OP

Dec ’20

OneNice,

I tracked this down to something specific to macOS and a Samba bug (Bug 14420). Try setting the following in your smb.conf. I've had no issues since.

Code Block fruit:zero_file_id = yes

0

Answer 3

OneNice OP

Dec ’20

Hi Ben---,

I tried adding to the config, but it didn't work for me :(
But fruit:zerofileid = yes by default, maybe i need to add something else to the config or somehow enable fruit?

0

Answer 4

Ben--- OP

Dec ’20

If you aren't loading fruit in vfs objects it won't have any effect. The default for that setting used to be yes and it was changed to no which is causing problems. Try explicitly setting "fruit:zerofileid = yes" in your smb.conf. The following is working for me and I was previously seeing the some problems you are. I omitted any values not related to macOS.

Code Block [global]
    ea support = yes
    fruit:aapl = yes
    fruit:copyfile = yes
[share]
    fruit:metadata = stream
    fruit:resource = stream
    fruit:zero_file_id = yes
    vfs objects = fruit streams_xattr

0