It is quite possible to create a share with a name which is incompatible with FAT32 naming limitations. When this happens everything works correctly (assuming that the name is also SMB compliant) except that shcmd will spam the log with errors, and no adjustment of the share's .cfg will be possible.
Similarily, shares differing only by their case (test, Test, TEST) are all perfectly valid (assuming of course that they are not exported over SMB -> which there is no requirement to do so) but due to FAT32 they will all share a common share .cfg file.
When shmd / emhttp finds a share name which is incompatible with FAT32 naming conventions, an algorithm to adjust the .cfg file on the flash drive should take place.
See https://forums.unraid.net/topic/75534-cant-pull-from-depositry/?tab=comments#comment-696730 for a real-world (albeit accidental) example.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.