search for: exclusive_oplocks_open

Hi, I'm facing an issue with at least two Samba servers in production both showing important number of log entries like: smbd[27355]: PANIC: assert failed at smbd/oplock.c(149): exclusive_oplocks_open>=0 Looking at the source code, this panic is triggered when the number of exclusive oplocks for a given file becomes negative. Once triggered for one smbd process, this process can generate more than a million log entries per day, causing both perf and space issues on server end, and poor pe...

...et different log entries. I assume it's the same problem only being logged differently as it's too much of a coinicidence. This is what I get. [2002/08/10 12:21:01, 3] smbd/oplock.c:oplock_break(890) oplock_break: returning success for dev = 303, inode = 2589371, file_id = 205 Current exclusive_oplocks_open = 0 [2002/08/10 12:21:01, 2] smbd/open.c:open_file(230) dniasoff opened file usr/package/etc/xinetd.d/swat read=Yes write=No (numopen=3) [2002/08/10 12:21:01, 3] smbd/process.c:process_smb(877) Transaction 768 of length 76 [2002/08/10 12:21:01, 3] smbd/process.c:switch_message(684) switch mes...

...2002/06/07 14:33:53, 2] smbd/close.c:close_normal_file(211) johny closed file O/a1/KO-I_X8-eh.dft (numopen=0) Current oplocks_open (exclusive = 0, levelII = 0) initial_break_processing: cannot find open file with dev = 900, inode = 1556900 file_id = 41allowing break to succeed. Current exclusive_oplocks_open = 0 [2002/06/07 14:33:53, 4] smbd/open.c:open_file_shared1(891) calling open_file with flags=0x0 flags2=0x0 mode=0764 [2002/06/07 14:33:53, 2] smbd/open.c:open_file(230) johny opened file O/a1/KO-I_X8-eh.dft read=Yes write=No (numopen=1) reply_ntcreate_and_X: fnum = 5005, open name = O/a1/...

...ient failure in oplock break in file 3d_daten/System_4000/Anwendungen_41~a.SLDASM <-----posible error> [2005/03/21 16:11:21, 3, effective(10001, 1000), real(10001, 0)] smbd/oplock.c:oplock_break(935) oplock_break: returning success for dev = fe03, inode = 507499042, file_id = 433 Current exclusive_oplocks_open = 0 [2005/03/21 16:11:21, 2, effective(10001, 1000), real(10001, 0)] smbd/open.c:open_file(245) konst07 opened file 3d_daten/System_4000/Anwendungen_41~a.SLDASM read=Yes write=No (numopen=3) [2005/03/21 16:12:03, 3, effective(10001, 1000), real(10001, 0)] smbd/process.c:timeout_processing(1332)...

.../24 09:30:05, 5] lib/util.c:show_msg(268) EXAMPLE 2 [2003/02/24 09:30:06, 5] smbd/uid.c:change_to_user(200) change_to_user uid=(0,99) gid=(0,99) [2003/02/24 09:30:06, 3] smbd/oplock.c:oplock_break(855) oplock_break: returning success for dev = 903, inode = 1507360, file_id = 13 Current exclusive_oplocks_open = 0 [2003/02/24 09:30:06, 2] smbd/open.c:check_share_mode(422) Share violation on file (4,1,2,28171,Brigittes Documents/Work/Invoices/A13C0000,fcbopen = 0, flags = 0) = 0 [2003/02/24 09:30:06, 2] smbd/open.c:open_file(213) brigitte opened file Brigittes Documents/Work/Invoices/A13C0000 read=Yes...

I'm hoping someone has some insight into a problem I'm currenty having, which is: No one is able to edit (in place) documents with Word 2000 on a samba (2.2.6) disk share. A user can open word and save a document to the share, but when they go to edit the document Word says "Word cannot complete the save due to a file permission error". From Microsoft KB Q211632 it appears