SMB error 0x80070032 when copying large directories

[HolyK]

// EDIT: Issue is fixed in NAS-119564 , wait for next release.

The error happens when "Allow files in this folder to have contents indexed" is UNchecked under Properties -> Advanced.
Note that VirtualBox un-checks this automtically for VM default path/directory.

---

Original post:

Howdey!

I am facing weird issues when copying large directories over SMB. Smaller ones(<10GB) are OK but the moment I take something like ~50GB I am getting various errors. I've tried more clients, various network connections and NIC cards. Restart of SMB and whole TrueNAS did not helped. I don't recall such issues back in TrueNAS 12.0-U7*/U8 I was running for ~year so it seems to be related to TrueNAS 13. More details bellow

Clients:
Client1: Win10 Pro 21H2 (19044.1466)
Client2: Win10 pro 22H2 (19045.2251)
//Both facing same issue

TrueNAS:
Current: TrueNAS-13.0-U3.1 // facing issues
Previous: 12.0-U7 and 12.0-U8 // don't recall such issues
HW info in my signature, anyway I don't believe this is HW related.

NIC (Client ... NAS):
Intel CT 1000 <-> HP ProCurve switch <-> pfSense <-> Intel I210 (Client no1 over LAN)
Realtek 2.5GbE <-> Realtek RTL8125 2.5GbE (Client no1 direct connection)
Intel CT 1000 <-> Intel I210 (Client no2 direct connection - 100% worked before)
Realtek (whatever) <-> HP ProCurve switch <-> pfSense <-> Intel I210 (Client no2. over LAN)

Issue description:
When I try to copy dirs with larger size (big files inside, like 70GB VM file) it fails with this weird error code 0x80070032. If I hit "Retry" the content gets copied but it seems fishy because if I try to delete the same directory it fails with with "Folder in Use". Checking network traffic i see "Error: STATUS_FILE_IS_A_DIRECTORY" for which MS DOCs translates to "The file that was specified as a target is a directory and the caller specified that it could be anything but a directory."
Note that if I try to copy the 70GB file which is inside that directory instead it works just fine.

SMB service aux params:

Code:

socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE
getwd cache = yes

Share checked options:

Code:

Enable Alternate Data Streams
Enable SMB2/3 Durable Handles

Screenshots bellow. I will be happy to open a bug report but i am not sure if this isn't a symptom of an already reported issue (I haven't found similar one opened). Hoping for SMB guru @anodos to chime in :)

If any further logs/debugs necessary let me know.

 

[anodos]

Can you PM me a debug?

 

[Lemming]

Also seeing this issue recently start on my server, I'm pushing about 10+GB files to it on a regular basis and getting this error each time.

On a whim just tried a smaller folder, 2.7GB total size with about 20 files, not an issue. Zipped straight onto the server as it should.

Edit, also just tried a much larger folder (500GB or so, with a number smaller files in it, again no issues. Seems to only affect folders with files in it that are multiple gigabytes in size.