I'm getting a lot of these messages in my logs: [2002/01/25 16:00:07, 0] smbd/oplock.c:request_oplock_break(995) request_oplock_break: no response received to oplock break request to \ pid 24440 on port 44511 for dev = 4809, inode = 24110 for dev = 4809, inode = 24110, tv_sec = 3c5156c5, tv_usec = 1a49d and people are complaining that their machines hang for minutes when trying to retrieve files. I suspect this can be related, but I have no clue what to do about it. This problem escalated after installing Office XP Pro, where it seems that word locks the file it loads but for some reason are unable to unlock them. This causes other machines to hang when they try to open these locked files. BTW: I'm running samba-2.2.0-15. Should I upgrade and if so, to which version? I don't feel like running a cvs-version at the moment, but can do so if it is strongly suggested. -- Johnny Ljunggren, B?refjellvn 15, 3160 STOKKE Tlf: 918 50 411, ICQ: 50630605
I just about had a heart attack with this one.... Try 1. Changing the NIC card. This makes it better but will not make it go away. 2. Remove all other protocols such as Netbeui, ipx if possible. Effectiveness of this was not seen. 3. Dump 2.2.2 and 2.2.1. Use 2.0.7. This one WORKS! You may not be able to use it since it does not have all the features. But this release works WAY faster and has no oplock problems at all. The 222 and 221 code is very buggy (despite its claims) and nobody has identified the problem. SB -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On Behalf Of Johnny Ljunggren Sent: Friday, January 25, 2002 9:15 AM To: samba@lists.samba.org Subject: Strange oplock-messages in samba-logs I'm getting a lot of these messages in my logs: [2002/01/25 16:00:07, 0] smbd/oplock.c:request_oplock_break(995) request_oplock_break: no response received to oplock break request to \ pid 24440 on port 44511 for dev = 4809, inode = 24110 for dev = 4809, inode = 24110, tv_sec = 3c5156c5, tv_usec = 1a49d and people are complaining that their machines hang for minutes when trying to retrieve files. I suspect this can be related, but I have no clue what to do about it. This problem escalated after installing Office XP Pro, where it seems that word locks the file it loads but for some reason are unable to unlock them. This causes other machines to hang when they try to open these locked files. BTW: I'm running samba-2.2.0-15. Should I upgrade and if so, to which version? I don't feel like running a cvs-version at the moment, but can do so if it is strongly suggested. -- Johnny Ljunggren, B?refjellvn 15, 3160 STOKKE Tlf: 918 50 411, ICQ: 50630605 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Sanjiv Bawa wrote:> > I just about had a heart attack with this one.... > > Try > 1. Changing the NIC card. This makes it better but will not make it go away. > 2. Remove all other protocols such as Netbeui, ipx if possible. > Effectiveness of this was not seen. > 3. Dump 2.2.2 and 2.2.1. Use 2.0.7. This one WORKS! You may not be able to > use it since it does not have all the features. But this release works WAY > faster and has no oplock problems at all. The 222 and 221 code is very buggy > (despite its claims) and nobody has identified the problem.If you can show any situation where using the older, buggier, less secure 2.0.7 release works where 2.2.2 (or better still the current 2.2 cvs) doesnt we would like to know about it. Samba 2.2 is a little fussier about oplocks, becouse otherewise it can leave a hung client with a an oplock - denying others access to files etc. Bad network cards make it worse. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net
Hello, I have recently migrated from Novell Netware file server to Samba 2.2.0-15. For couple days I wondered how could new my Samba server work so well ! However on next week users started complaining that their computers hang for minutes and displays errors (not found *.dll or fatal app error) when trying to start applications. Only Samba server restarting solved problems. It is related with oplocks so The black day log is such: In the day beginning: continiuos erros: [2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(761) oplock_break: end of file from client oplock_break failed for file FORPOST/ICONS/SCRDWN2.ICO (dev = 900, inode 229061). [2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(852) oplock_break: client failure in break - shutting down this smbd. also some others rare errors: [2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(852) oplock_break: client failure in break - shutting down this smbd. [2002/01/21 10:57:46, 0] smbd/oplock.c:oplock_break(768) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file FORPOST/ICONS/INFO.ICO (dev = 900, inode 229260). [2002/01/21 10:57:46, 0] smbd/oplock.c:oplock_break(841) oplock_break: client failure in oplock break in file FORPOST/ICONS/INFO.ICO [2002/01/21 10:58:24, 0] lib/util_sock.c:read_socket_data(479) read_socket_data: recv failure for 4. Error = Connection reset by peer [2002/01/21 11:06:02, 0] smbd/oplock.c:process_local_message(357) process_local_message: Received unsolicited break reply - dumping info. [2002/01/21 11:06:02, 0] smbd/oplock.c:process_local_message(372) process_local_message: unsolicited oplock break reply from pid 15199, port 1275, dev = 900, inode = 1357219 and at the day end continious errors: [2002/01/21 15:26:11, 0] smbd/oplock.c:request_oplock_break(995) request_oplock_break: no response received to oplock break request to pid 15966 on port 1649 for dev = 900, inode = 1880493 for dev = 900, inode = 1880493, tv_sec = 3c4c1457, tv_usec = 840a3 After I restarted server and till now I have to restart server periodically each several days.
hello did you get any positive answer about oplocks, smbd process hanged, socket in CLOSE WAIT etc... I have the same problems on samba 2.2.5 and I have to regress to samba 2.0.7 now, because my customer cannot bear this situation longer... :( Pascal