Hello All

I am running a Pi4 with Buster.

On the Pi itself, I can read and write files in a folder. I then shared the folder via samba. I can read the same files from a Linux client but if I change anything and try to save, I get the following error:

Could not rename partial file smb://raspberrypi.local/OUR_STUFF/Rick Stuff/Documents/filename.part.
Please check permissions.

The save operation leaves a filename.part on the server. I have to discard the save. Odd thing is, if I use 'save as' and rename the file, it writes fine.

The same thing happens if I create a file in the server from the Linux client.

Windows 11 client reads and writes with no issues.

The whole directory tree reads 0777 when on the server.

This appears to be a Linux permissions issue but I have no idea where; on the server or on the Linux client.

Here is my samba.conf:

[OUR_STUFF]
comment = shared folder
path = /home/pi/OUR_STUFF
browseable = yes
writeable = yes
only guest = no
create mask = 0777
directory mask = 0777
public = yes
guest ok = yes
force user = pi
force group = pi

Any ideas?

As far as I know Windows guest access to a remote share was disabled in version 10 (1709) so I assume you are connecting as user pi with a password. That would mean the client would have full read/write permissions as user pi.

How are you accessing the share from a linux computer? via file browser or manually mounting? Are you entering a username and password? It would make sense that you are accessing the share as guest and can read but probably not write to existing files owned by pi.

Thanks for your reply.

Windows accesses through file explorer and never asked(s) for a username or password.

I get to the server through the file manager in Linux. Again, no request for username or password.

Keep in mind that with SAMBA shares the server permissions and ownership overrides everything else, but restrictions can also be set in the SAMBA share or global configurations. The most restrictive permissions win.

This may not even apply here, I am not running SAMBA on a RPi so I cannot run tests, but I thought it worth mentioning.

It depends on the linux file browser itself and version but it probably asked for username and password (or anonymous aka guest) the first time you connected and you might of selected to remember it forever. The same goes for Windows, there is a select box for remember username and password that is usually checked by default.

You can also check the samba logs and see who connects to the share. I agree it is a permission issue and in my opinion there is no reason to connect using guest if that is the case.

I'm getting frustrated with this.
A little back history. I saw that pi had an update to bullseye so I went ahead and installed it. That's when everything went to crap. Could not for the life of me get samba to do anything with bullseye. Went back to buster and now can't get samba working on it correctly.
My biggest mistake was overwriting buster on my original sd card with bullseye. Word of warning to the wise, use a different sd card if you can.
Anyway what I just now did was install buster pi on a new sd card to start fresh.
Installed samba 4.9.5 and set up my pi user as a samba user with password. Both Windows and Linux can log in to samba share. Windows can read, write, create directories and files and save and delete same. Linux can do all that but cannot save file. Linux can create text file write to it but cannot save it. The error message in the op still pops up in Linux.

Culled my smb.conf share to this:

[shared]
path = /home/pi/shared
browseable = yes
writeable = yes
create mask = 0777
directory mask = 0777
public = no

I know it is a permissions issue but Linux worked fine with the old buster. I have no idea where to go from here.

See if this helps...
https://wiki.samba.org/index.php/Set...share_settings
This may also be of interest...
https://www.techrepublic.com/article...ng-with-samba/

BTW, can you show us the current permissions?

Another blog of interest...
https://work-work.work/blog/2018/12/...rity-mask.html
Validated by...
https://www.samba.org/samba/docs/cur...ORCECREATEMODE

While not exactly the same I have debian 11 VirtualBox virtual machine which runs samba 4.13.13. If I setup a similar share as #7 with a username/password as my real user this is what I see.
If I create a new directory from the file browser on the host which runs CentOS and create a directory on the debian 11 itself the permissions do match as expected. If I create a new text document from the host it isn't 0777 but don't know why at the moment. I can edit and save existing documents created in the VM from the host.

The output of ls -ld /home/pi/shared is:

drwxrwxrwx 3 pi pi 4096 Nov 22 15:10 /home/pi/shared

Hmmm...does the following samba directive change that behaviour?

Tried:

force create mode = 0777 no help

unix extensions = no no help



I'm beginning to suspect this may not be a permissions thing. Remember that when trying to save using Linux client, there is a partial file left over. I checked the permissions on that file and they are 777. Don't know if that has any bearing on this case.

No changes with unix extensions.

What application are you using to create / edit a file? What are the partial file names?

Some applications will create temporary files inside the same directory as the original file which may not may not get deleted when the original is closed. oplock files may or may mot be created.

Another directive that can impact on multi-user access behaviour...

For example:

Found that KDE Dolphin ver. 21.08.3 appears to be the problem here. Ran a PC with an older version of Dolphin 20.12.2 and it had no problems at all. Submitted a bug report to them. Waiting on a reply.

Should I mark this solved?

Thanks for all your inputs.