[Samba] Intermittent problem with samba & win2k

[dave cunningham]

   ------- Original message follows -------
>On Sat, 2002-11-16 at 15:07, dave cunningham wrote:
>> I'm new to linux & samba having just started using each within the last
>> month or so.
>>
>> I have a small LAN at home consisting of 2 win2k machines and a samba
>> file server (2.2.6) on a SuSE 7.3 box.
>>
>> I'm seeing intermittent problems accessing a samba share from each of
>> the two win2k machines and would appreciate any help in solving this.
>>
>> What I see is problems creating a new file or opening an excel file on
>> the server. There seems to be no problems at all in opening read only
>> files.


<snip>

>
>set your log file to <logdir>/%U_on_%m_from_%m.log, and see if you're
>getting oplock errors in that log.
>

Hi Christopher,

Thanks for taking an interest.

I've done as you suggested & so far as I can tell am not seeing oplock 
errors.

Trying to open file "Book1.xls" from computer name "echelon" as user 
"dee" I see the following in "dee_on_echelon_from_echelon.log":

[2002/11/17 15:10:26, 2] smbd/open.c:open_file(246)
   dee opened file Book1.xls read=Yes write=No (numopen=1)
[2002/11/17 15:10:26, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(186)
   linux_set_kernel_oplock: got kernel oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 8
[2002/11/17 15:10:26, 5] smbd/oplock.c:set_file_oplock(219)
   set_file_oplock: granted oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 8, tv_sec = 3dd7b162, tv_usec = af482
[2002/11/17 15:10:26, 5] smbd/nttrans.c:reply_ntcreate_and_X(995)
   reply_ntcreate_and_X: fnum = 10510, open name = Book1.xls


While in file "nobody_on_echelon_from_echelon.log" I see the following:

[2002/11/17 15:10:19, 2] smbd/open.c:open_file(246)
   dee opened file Book1.xls read=Yes write=Yes (numopen=3)
[2002/11/17 15:10:19, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(186)
   linux_set_kernel_oplock: got kernel oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 1613
[2002/11/17 15:10:19, 5] smbd/oplock.c:set_file_oplock(219)
   set_file_oplock: granted oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 1613, tv_sec = 3dd7b15b, tv_usec = b62bc
[2002/11/17 15:10:19, 5] smbd/nttrans.c:reply_ntcreate_and_X(995)
   reply_ntcreate_and_X: fnum = 13664, open name = Book1.xls


Additionally, in the preceding 4 seconds there are 12 messages in this 
file of the form:

[2002/11/17 15:10:16, 2] smbd/open.c:open_file(246)
   dee opened file Book1.xls read=Yes write=No (numopen=3)
[2002/11/17 15:10:16, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(186)
   linux_set_kernel_oplock: got kernel oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 1610
[2002/11/17 15:10:16, 5] smbd/oplock.c:set_file_oplock(219)
   set_file_oplock: granted oplock on file Book1.xls, dev = 305, inode = 272030, file_id = 1610, tv_sec = 3dd7b158, tv_usec = 18f75
[2002/11/17 15:10:16, 5] smbd/nttrans.c:reply_ntcreate_and_X(995)
   reply_ntcreate_and_X: fnum = 13661, open name = Book1.xls

Not knowing what these files are describing I cannot comment as to what 
this shows beyond noticing/guessing that a read/write lock seems to have 
been granted, on the requested file, according on the to the 'nobody...' 
log while the windows system appears not to have write access on this 
file.
-- 
Dave Cunningham
PGP Key <http://www.upsilon.org.uk/dc.asc>