SMB problem: autocomplete, synology, ls

[David Laidlaw]

I am getting 20-30 second hangs when I try to autocomplete in a Terminal window an SMB directory. For example:

% ls /Volumes/space/<TAB>​

locks up my terminal for 20-30 seconds before showing the potential completions. I can't ^C, even, so it is probably in some system call, I believe. This did not happen at some point in the past, but I cannot say if it is correlated with a particular OS release or Synology update. The machine "space" is a Synology NAS DS1815+ running DSM 6.2.4-25556 Update 2. The mac is an M1 air running Big Sur 11.6.1. I have over 300Mbps of wifi bandwidth from the mac to the wifi hub and GB ethernet from there to the Synology. Ping time from mac to synology is 8ms+-5ms.

Opening a finder window in a remote directory with ~2000 files in it also takes about 40 seconds, which seems longer to me than it used to.

Opening a finder window in a different remote directory with 15 items takes about 20 seconds. That is definitely longer than it used to be.

Any suggestions would be appreciated.

 

[HDFan]

Any possibility of directly connecting to the unit via ethernet to test? If it works that might point to some problem in the network.

Had no problems with a ssh to a 1019 DSM 7 via ethernet.

 

[David Laidlaw]

Any possibility of directly connecting to the unit via ethernet to test? If it works that might point to some problem in the network.

Had no problems with a ssh to a 1019 DSM 7 via ethernet.

Exactly the same behavior over wired 1G ethernet.

 

[HDFan]

OK. SMB also slow if wired.

1. If you run an iperf3 test from your Mac to the Synology, again wired, what results do you get?

iperf3 -c 10.0.0.30

Connecting to host 10.0.0.30, port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 107 MBytes 895 Mbits/sec
[ 5] 1.00-2.00 sec 105 MBytes 882 Mbits/sec
[ 5] 2.00-3.00 sec 109 MBytes 916 Mbits/sec
[ 5] 3.00-4.00 sec 109 MBytes 911 Mbits/sec
[ 5] 4.00-5.00 sec 109 MBytes 918 Mbits/sec
[ 5] 5.00-6.00 sec 110 MBytes 923 Mbits/sec
[ 5] 6.00-7.00 sec 107 MBytes 897 Mbits/sec
[ 5] 7.00-8.00 sec 110 MBytes 921 Mbits/sec
[ 5] 8.00-9.00 sec 102 MBytes 860 Mbits/sec
[ 5] 9.00-10.00 sec 111 MBytes 931 Mbits/sec

I'm assuming you are running gigabit ethernet.

2. Do you have any other systems, Mac or PC, which you can directly connect to the Synology to test?

3. Do you get the same results when logged in as a test user on the Mac?

4. Same results when booted in Safe Mode?

 

[David Laidlaw]

I am using GB ethernet.

Transcript below shows ping and (failed) iperf3.


dhl20.dhl(124) ping 192.168.1.137
ping 192.168.1.137
PING 192.168.1.137 (192.168.1.137): 56 data bytes
64 bytes from 192.168.1.137: icmp_seq=0 ttl=64 time=0.708 ms
64 bytes from 192.168.1.137: icmp_seq=1 ttl=64 time=0.740 ms
C-c C-c^C
--- 192.168.1.137 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.708/0.724/0.740/0.016 ms
dhl20.dhl(125) iperf3 -c 192.168.1.137
iperf3 -c 192.168.1.137
iperf3: error - unable to connect to server: Connection refused
dhl20.dhl(126)

I cannot run docker on synology -- it spins on "Loading" indefinite. I'm
restarting the synology.

I've downloaded iperf3 into docker. It closes "unexpectedly" every time
I try to start the container complaining that it needs a -c or -s flag. I
am not going to try troubleshooting iperf3...

Restarting the synology seems to have sped everything back up. I
should have tried that first...

 

[HDFan]

I cannot run docker on synology -- it spins on "Loading" indefinite.

Restarting the synology seems to have sped everything back up

Great! I can't get iperf3 to run via docker either, keeps crashing. Since it works perfectly on QNAP (a regular package) didn't think it would be a problem.