Bug 13192 - no write access, if share-name equals folder-name
Summary: no write access, if share-name equals folder-name
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.3.11
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-15 09:46 UTC by Konstantin Hollerith
Modified: 2024-01-06 01:17 UTC (History)
1 user (show)

See Also:


Attachments
Samba logs - no write access to share (17.99 KB, application/zip)
2017-12-15 09:46 UTC, Konstantin Hollerith
no flags Details
Samba logs - with write access to share (26.28 KB, application/zip)
2017-12-15 09:47 UTC, Konstantin Hollerith
no flags Details
Linux file permissions of the sahre (448 bytes, text/plain)
2017-12-15 09:47 UTC, Konstantin Hollerith
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Hollerith 2017-12-15 09:46:54 UTC
Created attachment 13869 [details]
Samba logs - no write access to share

If the name of the share and the name of the shared Folder are identically, users won't have any write access:


[data1]
 path = /share/data1
 writable = yes


Using this share, I don't have write access.

However, if I use this settings (notice the share name and the folder name differs), I have write access:

[data1_share_name]
 path = /share/data1
 writable = yes

Both times I tried to create the file "new-file-1.txt" with user "koni", I added the logs (log level = 5) for both.

Other People have this problem, too:
https://serverfault.com/a/557028

Server: Ubuntu 16.04.3 LTS
Filesystem: ext4
Samba: Samba version 4.3.11-Ubuntu
Client: Win7
Comment 1 Konstantin Hollerith 2017-12-15 09:47:23 UTC
Created attachment 13870 [details]
Samba logs - with write access to share
Comment 2 Konstantin Hollerith 2017-12-15 09:47:50 UTC
Created attachment 13871 [details]
Linux file permissions of the sahre
Comment 3 Björn Jacke 2024-01-06 01:17:01 UTC
So many shares have the same name as the directory that is shared. I'm pretty sure that you did set share ACLs for the problematic share in the past. Renaning the share effectively removes the share ACL, this is why the rename makes it work for you.