Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget
On Wed, 8 Sep 1999 20:47:15 +1000, hai scritto:>I have referred to the archive and some of you were having the oplock_break >problem. Does anyone have any solution for this? Will reboot fix the problem?>From the samba faq:==The advisory message means that you have either a defective network card on one of your clients, or else an MS Windows application is refusing to respond to an oplock break request from another MS Windows client that wishes to accessan already locked file. ==So check your nic's and cabling. If the above doesn't help, you can set "oplocks = no" (so did I) and the problem will disappear, though the performance may be affected negatively (I didn't notice).. If you can reproduce the error "whenever you want" (that is if it _always_ happens when you do a _certain_ operation), then write about it to samba-bugs@samba.org. -- giulioo@tiscalinet.it
>>I have referred to the archive and some of you were having the oplock_break >>problem. Does anyone have any solution for this? Will reboot fix theproblem?>>From the samba faq: >==>The advisory message means that you have either a defective network card >on one of your clients, or else an MS Windows application is refusing to >respond to an oplock break request from another MS Windows client that >wishes to accessan already locked file. >==>So check your nic's and cabling.There has to be another answer to this problem. I went from samba-1.9.18p10-52.4 on RedHat 5.2 to the 2.0.x release and back to 1.9.18 because of this problem. The *only* thing that changed was the version of Samba. The clients, network cards, cabling, etc., all stayed exactly the same. It's probably not very scientific, but a quick count of the number of times "oplock" occured in the samba logfiles revealed the following for ~120 clients: samba 2.0.3, running for 1 week = 549 times samba 1.9.18 running for 2 weeks = 37 times Ouch! The only other thing I can think of is a missing service pack or update to Windows. (We're using Win '95 clients.) Does anyone know if there's an update that addresses this problem? -Eric Eric Sisler Library Computer Technician Westminster Public Library Westminster, CO, USA esisler@westminster.lib.co.us Linux - don't fear the Penguin. Want to know what we use Linux for? Visit http://gromit.westminster.lib.co.us/linux
On Thu, 9 Sep 1999 04:33:09 +1000, hai scritto:>There has to be another answer to this problem. I went from >samba-1.9.18p10-52.4 on RedHat 5.2 to the 2.0.x release and back to 1.9.18 >because of this problem. The *only* thing that changed was the version of >Samba. The clients, network cards, cabling, etc., all stayed exactly the >same.I agree with you, I had this problem with samba-2.0.x and up. Never had with 1.9.18. No network changes. But JA told me, many times... :-), that the oplock code has not changed from 1.9.x to 2.0.x. -- giulioo@tiscalinet.it
>[..] >> I agree with you, I had this problem with samba-2.0.x and up. Never had >> with 1.9.18. No network changes. >> But JA told me, many times... :-), that the oplock code has not changed >> from 1.9.x to 2.0.x. >> > Ditto. We have also had the same problem with 2.0.x and up. With 1.9.18 > everything with oplocks seemed to work fine, but as soon as we upgraded to > the 2.0 series we started getting Oplock break resends and failures. > We've just disabled oplocks all-together. :(Well, just for the stats: Exactly the same phenomenon here... Roman.Hallo Bruce, Am 09.09.99, 23:04:10 hast du Folgendes geschrieben:
I have been plagued by the oplock_break problem ever since I first tried to go to Samba 2.0.1. I have tried successive versions of Samba as it has been released, but the problem still occurs. Because of a change in 2.0.x that fixes a problem with saving AutoCAD files, and better handling of guest access for print queues, I run a small Samba 2.0.x server that is used very lightly, and I never have any problems. However, my main Samba server with 200+ users must remain on 1.9.18p10. I believe the problem that occurs is that oplocks are left hanging on the server, and are never removed. After a period of time, all the shared memory that is allocated to file locking is filled, and the server starts sending garbage back to the clients when they request locks, confusing the clients and creating all sorts of strange behavior. This would explain why lightly used servers will not see the problem, and why Samba 2.0.x functions well for a period of time then starts failing. There are so many great features in Samba 2.0.x, I'd really like to start using it in production. I hope the Samba team can come up with a solution to this problem eventually, but to this point I get the feeling they don't even recognize this as a problem. I am running Samba on Solaris 2.6, with Win95, WinNT and WTS clients. -- --------------------------------------------------------------------- Jay D. Anderson John Deere Davenport Works Jay@Deere.com P.O. Box 4198 Phone: 319.388.4268 Fax: 319.388.4159 Davenport, Iowa 52808 http://www.dw.deere.com/~hz01930 http://web.infoave.net/~jaya
> > >There has to be another answer to this problem. I went from > >samba-1.9.18p10-52.4 on RedHat 5.2 to the 2.0.x release and back > to 1.9.18 > >because of this problem. The *only* thing that changed was the > version of > >Samba. The clients, network cards, cabling, etc., all stayed exactly the > >same. > > I agree with you, I had this problem with samba-2.0.x and up. Never had > with 1.9.18. No network changes. > But JA told me, many times... :-), that the oplock code has not changed > from 1.9.x to 2.0.x. >Ditto. We have also had the same problem with 2.0.x and up. With 1.9.18 everything with oplocks seemed to work fine, but as soon as we upgraded to the 2.0 series we started getting Oplock break resends and failures. We've just disabled oplocks all-together. :( Bruce btenison@rstc.cc.al.us ....and me, does any one know what the problem is?, we have had to go back to an older version !!!! Mick mt@symbionics.co.uk
Sorry to say so, but I have this problem with 1.9.18p10 (Debian 2.1 dist). The only way I solved this was to turn oplocks off which while not a fix at least the server is reliable now. This is not solely a 2.0.x problem. The server in question is serving to VSS & VC++ clients, and I get hundreds of these oplock breaks every day. Trevor tnuridin@tantalus.com.au>Ditto. We have also had the same problem with 2.0.x and up. With 1.9.18>everything with oplocks seemed to work fine, but as soon as we upgradedto>the 2.0 series we started getting Oplock break resends and failures. >We've just disabled oplocks all-together. :( > >Bruce >btenison@rstc.cc.al.us > >....and me, does any one know what the problem is?, we have had to go >back to an older version !!!! > >Mick >mt@symbionics.co.uk
Hello there, The problem I have is that the first time a client renames a file, say 1999.txt, using Windows Explorer the rename fails. The client machine displays an message box saying: "Cannot rename 1999.txt. Access is denied." Clicking OK on the message box and trying to rename the file again works ok. This happens consistently, but *only* the first time the client attempts to rename a file after they have logged in. In the smb.log file the following is written: [2000/04/24 14:06:38, 0] smbd/oplock.c:oplock_break(974) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file web/gsa/1999.txt (dev = 307, inode =2146408). [2000/04/24 14:06:38, 0] smbd/oplock.c:oplock_break(1048) oplock_break: client failure in oplock break in file web/gsa/1999.txt I've increased the oplock break time in smb.conf from 10 to 100 but with no discernablechange. FYI: Samba 2.0.6 running on RH 6.1 with 2.2.12 kernel. Clients are using NT4(SP6.) TIA Andrew Larcombe
Hi, I compiled and installed Samba version 2.2.2 on Solaris 2.6 and I have the following problem: On certain Windows stations, there is a delay of 2 minutes to open a file. And in the log of Samba for this station, I have the following result: [2002/09/30 11:03:02, 0] smbd/oplock.c:oplock_break(786) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file S380710.tif (dev = 1540008, inode = 24572). [2002/09/30 11:03:02, 0] smbd/oplock.c:oplock_break(859) oplock_break: client failure in oplock break in file S380710.tif What can I make to correct the problem. Thank you. _/\_______________________ Dominic Saindon Analyste en syst?me COGNICASE (Canada) inc. 2144, rue King Ouest, bureau 240 Sherbrooke (Qu?bec) J1J 2E8 T?l. : (819) 564-1199, poste 2282 T?l?c. : (819) 564-0868 Courriel : dominic.saindon@cognicase.com