I have a FreeNAS box with 40 or so SMB shares. Mostly works no problem. Except for this one share where I can't create folder sometimes based on the name of the folder.
I noticed, because if I browse to the share within Windows and create a "New Folder", I just get a "permission denied" error (I assume this is because explorer makes a folder named "New Folder" first and then changes the name later). But if I browse to the directory from within my WLS instance, and create the folder named 'test' via
mkdir, it creates it no problem.
Unless I try to make a folder 'New Folder' with
This seems to be the case with a bunch of random folders, and from the FreeNAS box itself, I can create these folders no problem. The folders also certainly don't exist before hand, but if I create with FreeNAS, I'm able to delete them no problem from the places mounting these shares. But then not able to create them again.
This sounds like one of those problems where I'd just reboot the box, but around ~100 or so people are using it so I am trying to do this with as little down time as possible.
This is still happening and I have no clue as to what's going on. Some test cases/examples that make no sense together
- Making a new folder in my Documents named "New Folder" and copying it to my share results in permission deined.
- Making a new folder called "New Folderx" in my Documents and copying it over works just fine. I can also rename this folder to anything except "New Folder"
- On the server itself, running
su -m brian -c 'mkdir "New Folder"'works no problem, and from Windows, I can rename or delete this folder.
- "New Folder" is just an example folder that doesn't work, other folder names also randomly have these exact same issues
- This is only true for the root of the share, inside other folders, I don't have these issues
some sanity checks
$ getfacl . # file: ../Share # owner: root # group: company group:super:rwxpDdaARWcCos:fd-----:allow owner@:rwxpDdaARWcCos:fd-----:allow group@:rwxpDdaARWcCos:fd-----:allow
$ groups brian brian super
$ sharesec -v 'Share' REVISION:1 CONTROL:SR|DP OWNER: GROUP: ACL:S-1-5-21-4096896313-3432959665-639265334-1283:ALLOWED/0x0/FULL ACL:S-1-5-21-4096896313-3432959665-639265334-1287:ALLOWED/0x0/FULL
$ net groupmap list | grep super super (S-1-5-21-4096896313-3432959665-639265334-1287) -> super