"The file '...' is too large for the destination file system

[Michael S. Steinebach]

I searched ... didn't find anything.

Since upgrading to 11.2-U2.1, attempts to copy files to my share result in the message provided in the post title.

Rolling back a version resolves the issue.

I've tried enabling SMBv1 support in my share, but that made no difference. Thoughts?

 

[Basil Hendroff]

Please describe your FreeNAS hardware, software and pool configuration. What client machine are you using?

 

[Michael S. Steinebach]

Much of the info requested is not relevant but

Dual CPU Xeon. 4x4TB WD Red Mirror. 48GB ECC Memory. FreeNAS 11.2-U2.1.

Clients are Windows 10 machines that are up-to-date on patches.

Again, not an issue in U1.

 

[Basil Hendroff]

How large is the file you're trying to copy? > 4GB? Can you figure out the size threshold before you get the error?

 

[jlpellet]

A few follow up questions - I think more details about the operation would help.
1) Is this copy attempt from the win10 or from FN & does the error msg appear on which side?
2) How long is the filename & does it use special characters?
3) I think win10 & BSD/Linux use a local copy in transferring the file so you may need enough free space on each side to hold an extra copy during the copy. Is free space limited on either end?

 

[Michael S. Steinebach]

Yes, larger than 4GB. From windows 10 to FN. Windows reports the error as soon as I initiate the copy.
No special characters. It's short, maybe 20.
Space is not an issue on either side.

 

[Basil Hendroff]

Do files just over 4GB copy ok? What about just under 4GB? You are using SMB shares and not WebDAV shares?

 

[Michael S. Steinebach]

In U1, yes. In U2, no. SMB

 

[anodos]

Can you post the output of testparm -s?

 

[Michael S. Steinebach]

I will as soon as I can get on a computer

 

[Michael S. Steinebach]

Can you post the output of testparm -s?

See attached file.

 

[Michael S. Steinebach]

Anyone have thoughts. I just upgraded to U3 and this is still an issue. I feel like it will be an issue going forward.

 

[Michael S. Steinebach]

I don't know the exact cutoff, but trying to transfer a 100MB file is too much. Small files (less than a few meg) seem to work.

 

[Basil Hendroff]

What makes this tricky is that no one else appears to have reported a similar issue in with 11.2.

Can you describe the network path that sits between the Win10 clients and the server?

 

[Michael S. Steinebach]

Cat 7 cable and some switches. Nothing too special. Again, I can take it back to U1 and it works. I did find another post about this but lost it and can't find it again. Gist was a recompiling of SMB related packages

 

[Basil Hendroff]

I'm moving huge files between 11.2 servers and clients. Is there something unusual about your 11.2 configuration?

 

[Basil Hendroff]

Do you get the error in both directions? Copying from the share as well as copying to the share?

 

[Michael S. Steinebach]

Entirely possible. I haven't needed to change anything since I set it up a few years ago on v10. I'll run back through the documentation.

 

[Basil Hendroff]

on v10.

You mean Corral?

 

[Michael S. Steinebach]

Yeah, corral. I did go to v11. 0 within a few months of my build