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

[Basil Hendroff]

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

There isn't an upgrade path from Corral to FreeNAS 11 so you would have had to do a new install of 11 and then import your pool. Does that sound about right?

 

[Michael S. Steinebach]

It does; obviously a long time ago

 

[Basil Hendroff]

Does the copy fail in both directions? From the share and to the share?

 

[anodos]

Does this happen immediately? If so, can you send me a pcap of the traffic? tcpdump -i <your interface> -p -s 0 -w /var/log/samba4/large_file_transfer.pcap host <ip of your Windows client> and port 445

You can press Control+c to stop the pcap, then click on System->Advanced->Save Debug to generate a debug file that contains the pcap. Once you have it PM the tar file to me.

 

[Metalnas]

So I'm having the same issue Michael is having. I did notice that if I create a new dataset I don't get the error about file size. I compared my existing data to the new dataset I create everything is exactly the same. So I'm very confused what changed?

 

[anodos]

So I'm having the same issue Michael is having. I did notice that if I create a new dataset I don't get the error about file size. I compared my existing data to the new dataset I create everything is exactly the same. So I'm very confused what changed?

Can you try turning off zfs_space and see if the problem continues on the dataset in question?

 

[Metalnas]

Can you try turning off zfs_space and see if the problem continues on the dataset in question?

So I turned off zfs_space and gave it like 5 mins before trying anything. But it didn't work so I reboot my freenas server. After the reboot I was able to copy files to the dataset I made changes to. But the test dataset I created has the zfs_space switch still enabled and I'm able to write files to that share still. Also I had the same issue with when I was running 11.2 u2.1 I updated to 11.2 u3 today hoping that would resolve the issue with copying files to my shares but it didn't.

 

[anodos]

So I turned off zfs_space and gave it like 5 mins before trying anything. But it didn't work so I reboot my freenas server. After the reboot I was able to copy files to the dataset I made changes to. But the test dataset I created has the zfs_space switch still enabled and I'm able to write files to that share still. Also I had the same issue with when I was running 11.2 u2.1 I updated to 11.2 u3 today hoping that would resolve the issue with copying files to my shares but it didn't.

Removing zfs_space will require restarting the SMB service (to be sure that client gets a clean connection). I don't quite follow your post. Is the problem intermittent?

 

[anodos]

So I turned off zfs_space and gave it like 5 mins before trying anything. But it didn't work so I reboot my freenas server. After the reboot I was able to copy files to the dataset I made changes to. But the test dataset I created has the zfs_space switch still enabled and I'm able to write files to that share still. Also I had the same issue with when I was running 11.2 u2.1 I updated to 11.2 u3 today hoping that would resolve the issue with copying files to my shares but it didn't.

Can you post the output of zfs get all <pool>/<dataset> of the dataset where the share resides?

 

[Michael S. Steinebach]

For me, I can read and copy files off, but I just can't write.

I went back through the setup guide and didn't find anything that stood out. I rolled back to U1 and of course, things work as previously stated. After I get some files moved over, I'll put it back to U3 and try the steps provided above.

 

[Michael S. Steinebach]

Glad to see I'm not the only one...

 

[anodos]

The problem appears to be caused by having aio_fork set. Remove the vfs object.

 

[Michael S. Steinebach]

Yup! That did it. Disabled aio_fork, restarted SMB, writing now works.

Thanks!