[Samba] Clients can't write to group-writable files

Josh Malone jmalone at nrao.edu
Tue Nov 15 21:42:11 UTC 2016


On 11/10/16 1:13 PM, Josh Malone wrote:
> Hello,
>
> Really stumped on this issue. I have samba 4.4.7 running on a new
> server. Users cannot write to files to which they have write permissions
> via group.
>
> Example:
>
> Here's the local filesystem on the samba server. I'm logged in as jmalone
>
>
> : jmalone at canis; cd /home/www.nrao.edu/content/logs/
> : jmalone at canis; ls -l
> total 4
> -rw-rw-r-- 1 jmalone         nraoweb  0 Nov 10 10:02 baz
> -rw-rw-r-- 1 pmurphy         cvweb    0 Nov 10 11:09 foobar
> : jmalone at canis; touch foobar
>
>
> No problems. Now, let me mount that on my Mac:
>
>
> : jmalone at agrajag; cd /Volumes/www.nrao.edu/content/logs
> : jmalone at agrajag; ls -l
> total 2
> -rwx------  1 jmalone  nraocv   0 Nov 10 10:02 baz
> -rwx------  1 jmalone  nraocv   0 Nov 10 11:09 foobar
> -rwx------  1 jmalone  nraocv  44 Nov 13  2006 index.html
> : jmalone at agrajag.cv; touch foobar
> touch: foobar: Permission denied
>
> I can write to 'baz' though.
>
> Here's the log entries from the failed write attempt:
>
> [2016/11/10 10:01:58.250031,  2] ../source3/smbd/open.c:1025(open_file)
>   jmalone opened file content/logs/foobar read=No write=No (numopen=4)
> [2016/11/10 10:01:58.251220,  2]
> ../source3/smbd/close.c:793(close_normal_file)
>   jmalone closed file content/logs/foobar (numopen=3) NT_STATUS_NOT_FOUND
> [2016/11/10 10:01:58.252517,  2] ../source3/smbd/open.c:1025(open_file)
>   jmalone opened file content/logs/foobar read=No write=No (numopen=4)
> [2016/11/10 10:01:58.253723,  2]
> ../source3/smbd/close.c:793(close_normal_file)
>   jmalone closed file content/logs/foobar (numopen=3) NT_STATUS_NOT_FOUND
>
>
> The listing is weird over cifs too - not sure if that's the source of
> problems or a symptom, or a red herring. I also get the same error on a
> Windows smb client. I've tried 4.5.1, 4.4.5, and now 4.3.12 and they all
> do the same thing. My old server running 4.0 didn't have this issue.
>
> In case it matters, the filesystem being shared via samba is NFS mounted
> to the samba server.
>
> Thanks so much,
>
> -Josh


I cannot fix this under RHEL6. I've tried every version of samba back to 
4.0.

However - I just noticed that this bug DOESN'T occur on samba-gb. What's 
the difference? I've tried 2 different systems in CV and the bug occurs. 
GB's smb.conf doesn't look very different from what I'm testing with 
(colin.cv).

What gives, man?

-Josh

-- 
--------------------------------------------------------
        Joshua Malone       Systems Administrator
      (jmalone at nrao.edu)    NRAO Charlottesville
         434-296-0263           www.nrao.edu
	434-249-5699 (mobile)
--------------------------------------------------------



More information about the samba mailing list