Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.
On a Mac, I have a folder named "AUX.2016.03.09" with 61 files within. If I copy it (using sudo cp -a) to an SMB share on my FreeNAS 11.2-U7:
1) cp on the Mac reports various "No such file or directory" errors.
2) The resulting folder name gets mangled to "AG7JL4~7.09" (an 8.3 name?) when viewed from Finder over SMB. When ssh'ed to the FreeNAS, the folder name on disk is correct.
3) Only one of its 61 files is copied (either viewed over SMB or on the disk itself)
4) Trying to open the folder from Finder results in the folder disappearing.
Happily I can repro this. I increased Samba logging to "debug" and attach the logs here, as well as the command used on the Mac and its output.
Problem/Justification
None
Impact
None
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Sean McBride
January 8, 2020 at 6:16 PM
Wow, nice find. How delightfully obscure! 🙂
Andrew Walker
December 26, 2019 at 5:55 PM
There is not a bug here. Your files start with the name "AUX.", and these are reserved names in WIN32.
Do not use the following reserved names for the name of a file:
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended. For more information, see Namespaces.
I updated my test system from 11.3beta1 to 11.3rc1 and I still repro this.
Andrew, do you not agree there is a bug here?
Sean McBride
November 26, 2019 at 5:47 PM
I'm surprised you don't repro, it occurs trivially for me.
So I've just download the 11.3b1 ISO, created a VM, added a simple pool, created a single SMB dataset, added a single user, created a single share, connected from Finder, copied that same folder, and it repros immediately. I'll attach a debug. I can send you the whole VM if you'd like.
Andrew Walker
November 26, 2019 at 11:58 AM
(edited)
The only path component being mangled is "AUX.2016.03.09" -> "AG7JL4~7.09". Your file names aren't being mangled. If you provide a debug I can take a closer look at the issue, but as things stand I can't reproduce it.
On a Mac, I have a folder named "AUX.2016.03.09" with 61 files within. If I copy it (using sudo cp -a) to an SMB share on my FreeNAS 11.2-U7:
1) cp on the Mac reports various "No such file or directory" errors.
2) The resulting folder name gets mangled to "AG7JL4~7.09" (an 8.3 name?) when viewed from Finder over SMB. When ssh'ed to the FreeNAS, the folder name on disk is correct.
3) Only one of its 61 files is copied (either viewed over SMB or on the disk itself)
4) Trying to open the folder from Finder results in the folder disappearing.
Happily I can repro this. I increased Samba logging to "debug" and attach the logs here, as well as the command used on the Mac and its output.