I'm running FreeNAS-9.1.1-RELEASE-x64 (a752d35) and I am seeing a very strange file permissions problem while accessing a CIFS share from my Windows 7 machine:
1) navigate to the share folder (\\freenas\share) with Windows Explorer
2) right click and select New->Text Document, name it foo.txt
3) open the file with gvim (a file called .foo.txt.swp is created)
At this point I can exit gvim, .foo.txt.swp will be deleted, and I can delete foo.txt. If I continue with the next step things get weird.
4) enter some text into the file, save it, and quit gvim
Now a file called 4913 appears in the current directory. The Read-Only attribute is set on this file and foo.txt. If I try to delete either file I get an error that says "This action can't be completed because the file is open in another program". If I try to remove the Read-Only attribute I get an error that says "An error occurred applying attributes to the file: \\freenas\share\4913 Access is denied." The only way to remove the files is to SSH into FreeNAS and delete them from the Unix command line.
Can anyone shed some light on what is causing this?
1) navigate to the share folder (\\freenas\share) with Windows Explorer
2) right click and select New->Text Document, name it foo.txt
3) open the file with gvim (a file called .foo.txt.swp is created)
At this point I can exit gvim, .foo.txt.swp will be deleted, and I can delete foo.txt. If I continue with the next step things get weird.
4) enter some text into the file, save it, and quit gvim
Now a file called 4913 appears in the current directory. The Read-Only attribute is set on this file and foo.txt. If I try to delete either file I get an error that says "This action can't be completed because the file is open in another program". If I try to remove the Read-Only attribute I get an error that says "An error occurred applying attributes to the file: \\freenas\share\4913 Access is denied." The only way to remove the files is to SSH into FreeNAS and delete them from the Unix command line.
Can anyone shed some light on what is causing this?