Share violations with 0 open files???
Russell Senior
seniorr at aracnet.com
Mon Jul 16 20:39:45 GMT 2001
I have Samba 2.2.1 running for some clients in a small office.
Basically two people running Windows ME. They have been reporting
various slowness accessing Access database files located on the
server. I have been collecting level 2 logs, and one pattern has me
confused:
[2001/07/16 13:27:47, 2] /src/samba-2.2.1/source/smbd/open.c:open_file(216)
FRED opened file FOO/FOOData.mdb read=Yes write=No (numopen=3)
[2001/07/16 13:27:47, 2] /src/samba-2.2.1/source/smbd/close.c:close_normal_file(205)
fred closed file FOO/FOOData.mdb (numopen=2)
[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/close.c:close_normal_file(205)
fred closed file FOO/FOOData.mdb (numopen=1)
[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/open.c:open_file(216)
FRED opened file FOO/FOOData.mdb read=Yes write=No (numopen=2)
[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/close.c:close_normal_file(205)
fred closed file FOO/FOOData.mdb (numopen=1)
[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/close.c:close_normal_file(205)
fred closed file FOO/FOOData.ldb (numopen=0)
a->[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/open.c:check_share_mode(426)
Share violation on file (0,4,2,21084,FOO/FOOData.ldb,fcbopen = 0, flags = 0) = 0
[2001/07/16 13:28:26, 2] /src/samba-2.2.1/source/smbd/open.c:open_file(216)
FRED opened file FOO/FOOData.ldb read=Yes write=No (numopen=1)
[2001/07/16 13:29:32, 2] /src/samba-2.2.1/source/smbd/open.c:open_file(216)
The thing that's got me confused is that according to these logs
(assuming I am reading them correctly), there are no files open as of
point a. If there are no files open, how can there be a share
violation? Is something going haywire?
--
Russell Senior ``The two chiefs turned to each other.
seniorr at aracnet.com Bellison uncorked a flood of horrible
profanity, which, translated meant, `This is
extremely unusual.' ''
More information about the samba-technical
mailing list