Bug 3995 - CIFS share mounted by mount.cifs not readable, only writeable
Summary: CIFS share mounted by mount.cifs not readable, only writeable
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.23a
Hardware: x86 Linux
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2006-08-03 09:32 UTC by Matthew Williams
Modified: 2006-08-03 10:04 UTC (History)
0 users

See Also:

Edited log file from failed read attempt (22.47 KB, text/plain)
2006-08-03 10:01 UTC, Matthew Williams
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Williams 2006-08-03 09:32:35 UTC
I have a Samba server with multiple shares.  I have a mix of both Windows and Linux clients that access those shares.  When I upgraded from 3.0.21c to 3.0.23a, I found that the Linux clients could no longer read any of the files on the shares.  The strange thing is that they still had write access.  Windows clients were unaffected by this problem and could read/write as before.


cd /mount-point            # no problem
echo "hello" > test_file   # no problem
cat test_file
** Permission denied **

Reading the file on a Windows client and directly on the server shows that the file is indeed created and contains "hello".

Downgrading back to 3.0.21c fixed the problem with no other changes on client and server.

I am running kernel on both server and client and am aware of the isses with kernel oplocks in 2.6.17, but have them disabled through smb.conf as all access to these files is through Samba.

I captured a level 10 log of an attempted read.  I'll post it in a follow-up comment.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2006-08-03 09:57:23 UTC
Fixed in 3.0.23b (to be released shortly).
Comment 2 Matthew Williams 2006-08-03 10:01:02 UTC
Created attachment 2081 [details]
Edited log file from failed read attempt

I've snipped stuff that I *think* is not relevant from the beginning and end of the log file and did a search and replace on SIDs.  I still have the log file in its entirety if I cut away too much stuff.

The interesting part is around line 497 when an NT_STATUS_ACCESS_DENIED message is sent back to the client.
Comment 3 Matthew Williams 2006-08-03 10:04:39 UTC
Wow, 25 minutes from open to resolved!