Created attachment 18628 [details] server log file System: Arch Linux Arm on Raspberry Pi 5 (aarch64) Error message on client: "The file '<%1 NULL:NameDest>' is too large for the destination file system" Steps to reproduce: 1. mount exfat file system (kernel driver or exfat-fuse) 2. create share on mounted file system 3. try to create or copy a folder to the share (e.g. from Windows) Additional comments: - Bug is newly introduced in 4.22.0 (4.21.5 and before works fine). - All other operations including renaming or deleting folders are not affected.
Can you try setting vfs mkdir use tmp name = no for the share?
With this directive it works again.
Great! I guess there's not much more we can do. Afaict we can't easily detect this automatically that the filesystem we're sharing has a restricted characterset.
Thanks for guiding the right way... However, the issue occurs due to the colons included in the temporary name. While this is a valid character on linux filesystems the error should be thrown on all Microsoft developed ones, including fat(32) and ntfs. This may be quite some restriction of the default setting. Using a different commonly accepted character such as an underscore would be an overall and in my idea easy solution. Alternatively the underlying filesystem can be checked with 'stat' to avoid using an illegal character. A third but for the user less convenient solution would be referencing this limitation in the man pages. Just my two cents.
This bug was referenced in samba master: c2b74ef093aff6175ef8e4572a203e5beacc527f
Created attachment 18634 [details] fix for 4.22
Pushed to autobuild-v4-22-test.
This bug was referenced in samba v4-22-test: 417feb2851a8d42d47577dc2446ada7d9b9849bb
This bug was referenced in samba v4-22-stable (Release samba-4.22.1): 417feb2851a8d42d47577dc2446ada7d9b9849bb
Closing out bug report. Thanks!