NFS and SMB share "lag on connect" since 25.10 upgrade from linux/windows clients

TrueNAS General
,
1

I upgraded truenas scale from 25.04.2.5 to 25.10.0

Since the upgrade SMB/NFS clients see a “lag” when accessing a share from truenas

From Almalinux 10 and Ubuntu 24.04 clients, when accessing an NFS share, there is an “half second” lag before the content of the share is seen (“ls -la /share” …)

From WIndows 10 file explore, sometime the content of an SMB network drive does show up after half a second “lag” or sometimes do not appear at all. Closing/opening the file explorer solves the problem. This happens on multiple different shares, some shared via SMB and NFS, some only via NFS, other only in SMB etc

After that “initial connect”, everything seems OK

Everything was working well with v25.04 and nothing has changed on the truenas server except the upgrade, nor on the Linux/Windows clients

I have no idea where to start to try to debug

Are we the only one with this problem?

2 Likes
2

Do you see this on local filesystem? There’s really no commonality between the NFS and SMB server in TrueNAS, and so it being protocol-specific is unlikely.

3

I have seen a couple posts here about lags in SMB access.

I upgraded my home production TN to 25.10 as soon as 25.10.0 hit and I was coming from 25.4.2.5.

I just tried on my Windows 10 laptop and did not see any lag.

I just tried on my MacOS laptop and did not see any more than the usual Finder lag.

On the Windows system I am connecting by IP address and not name.

On the MacOS system I am connecting by name.

I am not saying there is not a problem, just that I have not been able to duplicate it.

4

Well, i just tried 25.10 and changed back quickly.

first of all the dashboard/webgui seems wobbly, when i browsed around a bit and returned to the dashboard the graphics didnt load until i hit reload in the browser.

furthermore and more to the point is that when creating new directories on 25.10 they don’t show up immediately in the explorer window, i need to F5 to see it. on 24.latest i see it immediately, no need for refresh.

5

Do you see this on local filesystem

What do you mean? you want me to mount the share NFS or SMB directly on truenas?

and so it being protocol-specific is unlikely.

BTW iperf3 perfs from various clients to the truenas server are excellent, same as before: about 9.7Gb/s on 10Gb link…(mtu=9000 + a few optimisations here and there, nothing changed during/after upgrade)

6

What do you mean? you want me to mount the share NFS or SMB directly on truenas?

SSH in and run ls -l in the share path?

7

Same problem with SMB share of 25.10 on windows 11! Files and directories in the samba shared folders cannot be fully load sometimes. The folder also may appear empty. After manually refresh, the contents in the folder appear again.
This issue does not happen in version 25.04. It just appeared after upgrading to 25.10.

2 Likes
8

Ah this sounds exactly like what I have been chasing since upgrading to 25.10RC1

My Emby and Jellyfin Servers run in a W11 VM, and connect to my media via SMB shares.

Both servers are often just “missing” loads of shows and movies from their libraries and I have to rescan. These scans also take hours now, like 2-3 hours, vs minutes when using 25.04

3 Likes
9

SSH in and run ls -l in the share path?

ok(?). works perfectly…

I don’ t know if that helps, one example of shared dataset mount point:

mount
POOL-ZFS01/DS-X on /mnt/POOL-ZFS01/DS-X type zfs (rw,relatime,xattr,nfs4acl,casesensitive)
10

I have the same problem. I couldn’t find anything suspicious in the Windows or TrueNAS logs. I reverted to version 25.04.

1 Like
11

Are any of you experiencing the issue using access based enumeration? That can take a second for the list to get created and sent to the client.

12

nope not me, its greyed out even, this seems to be a real issue?

13

Are any of you experiencing the issue using access based enumeration?

this option is disabled for me

14

Can confirm this is affecting me as well.

I use FreeFileSync to back things up from my main PC to my TrueNAS instance (and back things up FROM TrueNAS to my external backup) and it would end up thinking that a large proportion of files didn’t exist on the NAS at all even when they did.

I restarted my PC, I restarted my TrueNAS Server, I did a scrub because I wondered if it was a dying drive, I recreated the shares, I deleted and recreated credentials, the only fix was rolling back to 25.04.2.5.

2 Likes
15

There is an open ticket for this at Jira

The symptoms seem to vary somewhat between users, but the issue is definitely real, and reverting to 25.04.2.5 fixes it.

2 Likes
16

Note that SMB uses two completely different authentication paths for IP vs DNS. That can result in substantial performance differences if one path is bugged. So it’s important to try both when troubleshooting.

A bug in Synology resulted in literal 100x performance loss using DNS.

17

Even locally on the LAN, such as using truenas.local as the address to connect to via SMB?

18

Probably, can’t say sure. As soon as you use DNS it uses Kerberos for authentication whereas IP uses NTLM. So if there is a bug in either NTLM or Kerberos share permission handling it can cause long timeouts for every single file being listed or read out written.a

19

i only use ip as did my friend, this is a real issue and need some priority i believe :o

20

It makes no difference here, \\truenas\path\to\my\files is a bad as \\192.168.0.20\path\to\my\files

1 Like