"DOS error: object name invalid" when transferring many large files

[midwan]

@obarthel
I've been troubleshooting a weird problem regarding smbfs in my environments. It seems that when trying to copy over several large files, after a certain point the operation throws an error DOS error: object name invalid and freezes the filesystem. With the older version of smbfs from Aminet, it will just freeze the filesystem without even throwing the error.

• I'm testing by copying a directory which contains several MPEG video files, sized from 40-120MB each. The source is a Samba share on my NAS, the destination is the Amiga side (tested both real and emulated environments, see below).
• The total size of the directory is around 2.9GB.
• No files contain any strange or very long filenames.
• The destination HDD is a) SDcard formatted with PFS3Aio and b) local NTFS HDD when using WinUAE

Test environments:

1. Real A600 with V2 Vampire accelerator. Runs 3.9, latest Roadshow, prism2 Wifi driver, smbfs.
2. WinUAE, OS3.9, latest Roadshow, X-Surf 100 ethernet driver, smbfs
3. WinUAE, running AmigaOS 3.1.4.1, internal bsdsocket.library emulation (no TCP stack running), smbfs
4. WinUAE, OS3.9, latest Roadshow, X-Surf 100 ethernet driver, FTP client (AmiTradeCenter) - this is to test if Roadshow itself has the same problem (it doesn't).

Here are my test results:

• A600 V2, RoadShow, prism2, smbfs, copy to local HDD: FAIL to copy files (freeze after several files are copied).
• WinUAE, RoadShow, X-Surf-100, smbfs, copy to SDcard: FAIL after 729.165.860 bytes
• WinUAE, RoadShow, X-Surf-100, smbfs, copy to local HDD: FAIL after 2,110,064,756 bytes
• WinUAE, RoadShow, X-Surf-100, smbfs, copy to local HDD test 2: FAIL (various files end up smaller than expected, e.g. 4MB instead of 40MB)
• WinUAE, RoadShow, X-Surf-100, smbfs compiled from source, copy to local HDD: FAIL with DOS error: object name invalid after copying 1.22GB of data.
• WinUAE, RoadShow, X-Surf-100, FTP client, download to local HDD: WORKS
• WinUAE, bsdsocket.library emulation, smbfs, copy to SDcard: WORKS

Interestingly, if I didn't use a TCP stack in emulation, smbfs seemed to work without the problem in my tests above. But in all the other cases, it fails at some point during the copy operation (not always the same point!).

Is there anything else I can do to help troubleshoot this?