I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:08, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:27, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:29, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f smbstatus reports that I have an EXCLUSIVE+BATCH oplock on the file. Other documents (text, image, audio, etc) work without problems as long as they're not associated with an Office app. The office files don't seem to be corrupted either - if I ftp them to my w2k workstation I can then open them locally. I tried setting fake oplocks yes/no but that didn't seem to change anything. Any suggestions/solutions? thanks, Nate Partenheimer Information Resources Butler University npartenh@butler.edu
Nate, The log messages indicate that samba believes that the user being serviced by smbd with pid# 2252 has an oplock on the file, and when another client (the one that is generating this oplock break log messaga) tried to open the file, HIS smbd recognized that there was an oplock held on this file, and send an oplock break request to that pid, and never got a response. It would be interesting to know if at the time you see these messages, if the pid noted in the message shows up in a ps -ef|grep -i smb. It could indicate that this smbd process is either hung, or perhaps aborted without cleaning up it's oplocks... I haven't looked at this part of the code to determine if that is possible or not. Also, what has changed since your users have complained about this - new version of samba? new version of MS Office on the pc's? New opsys on the pc's? Does stopping and restarting samba clear this up? Hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Wednesday, March 07, 2001 10:56 AM To: samba@lists.samba.org Subject: Explorer & MS Office hang Sensitivity: Confidential I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:08, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:27, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:29, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f smbstatus reports that I have an EXCLUSIVE+BATCH oplock on the file. Other documents (text, image, audio, etc) work without problems as long as they're not associated with an Office app. The office files don't seem to be corrupted either - if I ftp them to my w2k workstation I can then open them locally. I tried setting fake oplocks yes/no but that didn't seem to change anything. Any suggestions/solutions? thanks, Nate Partenheimer Information Resources Butler University npartenh@butler.edu -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Hi Nate, The interesting thing you mention is that Samba does not come down cleanly. Those smbd's that you are having to kill -9 usually indicates that the smbd is hung or spinning in some sort of loop; which would explain why you are not getting an oplock break reply from them. If you are the only one accessing the file, then the most likely senario is that the smbd that you were attached to when you opened the file got in this 'bad' state, and your pc did an autoreconnect the next time you tried to access anything on that server (which would spawn a NEW smbd). Then when you try to access the file, your NEW smbd tries to send an oplock break to the old smbd, which is hung and not replying. What we'll need to find out from the logs is WHAT the old smbd was doing right before you got your reconnection. A couple of ways to do this: in smb.conf set log file = <path>/log.%m log level = 10 debug pid = yes debug timestamp = yes This will give us a log file named log.<your client netbios machine name> the timestamp and pid debug will show us if during this problem, you end up reattaching to a different smbd, and also will let us see if the pid that the oplock message is complaining about is INDEED the previous smbd pid that you were connected to when you opened the file. These debug messages are gonna slow samba up quite a bit, so I would suggest you make a copy of your smb.conf file in the same directory with these changes, and name it smb.conf.<your client netbios machine name> and add the following line in your 'real' smb.conf file: config file = <path>/smb.conf.%m That way, only YOUR client will end up getting this high debug level, and everyone else can continue work unaffected. Let me know what you find out. hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Wednesday, March 07, 2001 11:17 AM To: "MCCALLDON "@envelope.hp.com; HP-USA@envelope.hp.com; ex1 " Subject: Re: RE: Explorer & MS Office hang Sensitivity: Confidential I'm the only one trying to access the file. It may be locked from trying to open it earlier but I'm never able to open it. We have a mixed environment with everything from win95->w2k and various versions of macOS. The only notable new thing is a win2k server. Restarting does not clear this up - in fact I have a bunch of smbd processes that won't die nicely. Usually, killing the original smbd process will kill and clean up all of them - not so anymore. It still manages most of them but about 10% aren't killed and I've terminated them with a kill -9. This seems to affect all versions of Office on both mac and pc. I even disabled my antivirus software to make sure it isn't interfering. I'll check what's logged against what's actually happening - process id's and locks - and get that to you if it will be helpful - I have some unhappy users. Thanks for your time and if this gives you any ideas plaes let me know. Nate ===========================================================From: "MCCALL,DON (HP-USA,ex1)" <don_mccall@hp.com> Date: 2001/03/07 Wed AM 09:07:27 EST To: "'npartenh@butler.edu'" <npartenh@butler.edu>, samba@us5.samba.org Subject: RE: Explorer & MS Office hang Nate, The log messages indicate that samba believes that the user being serviced by smbd with pid# 2252 has an oplock on the file, and when another client (the one that is generating this oplock break log messaga) tried to open the file, HIS smbd recognized that there was an oplock held on this file, and send an oplock break request to that pid, and never got a response. It would be interesting to know if at the time you see these messages, if the pid noted in the message shows up in a ps -ef|grep -i smb. It could indicate that this smbd process is either hung, or perhaps aborted without cleaning up it's oplocks... I haven't looked at this part of the code to determine if that is possible or not. Also, what has changed since your users have complained about this - new version of samba? new version of MS Office on the pc's? New opsys on the pc's? Does stopping and restarting samba clear this up? Hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Wednesday, March 07, 2001 10:56 AM To: samba@lists.samba.org Subject: Explorer & MS Office hang Sensitivity: Confidential I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:08, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:27, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:29, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f smbstatus reports that I have an EXCLUSIVE+BATCH oplock on the file. Other documents (text, image, audio, etc) work without problems as long as they're not associated with an Office app. The office files don't seem to be corrupted either - if I ftp them to my w2k workstation I can then open them locally. I tried setting fake oplocks yes/no but that didn't seem to change anything. Any suggestions/solutions? thanks, Nate Partenheimer Information Resources Butler University npartenh@butler.edu -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba ============================================================
Hi Nate, Looking at the log, what I am seeing is that the .doc file is opened requesting an oplock, which is granted, and then a bit later on another request from the client comes in to access the .doc file, which requires us to break the oplock; we recognize that WE are actually the one that HAS the oplock, so we break our own oplock (this is ok), and then actually LOCK the file using an fcntl() unix lock command. It is at the fcntl() lock request that the smbd appears to be hanging, because you will note that the next debugging info comes from a different pid, and the negot protocol, session setup, etc. starts over again for your client. So the issue appears that the fcntl lock request is hanging for some reason on your system. Tell me more about the filesystem that this share is on. Is it HFS, JFS, or is it an nfs mounted filesystem? switch message SMBlockingX (pid 14889) [2001/03/09 13:56:10, 5, pid=14889] smbd/uid.c:become_user(264) become_user uid=(0,1027) gid=(0,10) [2001/03/09 13:56:10, 3, pid=14889] lib/doscalls.c:dos_ChDir(342) dos_ChDir to /home/npartenh/mail [2001/03/09 13:56:10, 10, pid=14889] smbd/reply.c:reply_lockingX(4228) reply_lockingX: lock start=2147483539, len=1 for file outlinepl365.doc [2001/03/09 13:56:10, 10, pid=14889] locking/locking.c:do_lock(113) do_lock: lock type 2 start=2147483539 len=1 requested for file outlinepl365.doc [2001/03/09 13:56:10, 8, pid=14889] lib/util.c:fcntl_lock(2672) fcntl_lock 8 34 2147483539 1 2 [2001/03/09 13:57:13, 6, pid=14926] param/loadparm.c:lp_file_list_changed(1883) lp_file_list_changed() -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Friday, March 09, 2001 2:42 PM To: "MCCALLDON "@letter.hp.com; HP-USA@letter.hp.com; ex1 " Subject: RE: RE: Explorer & MS Office hang Sensitivity: Confidential Here's a log at level 10 - hope you can receieve it - any help would be appreciated. I opened a file - it hung in MS word, I killed it after a while, deleted the word temp file and tried again. Also - when I kill samba the process that was mine - for the open file - doesn't die nicely - I have to kill -9 it seperately. thanks, Nate ===========================================================From: "MCCALL,DON (HP-USA,ex1)" <don_mccall@hp.com> Date: 2001/03/07 Wed AM 10:00:36 EST To: "'npartenh@butler.edu'" <npartenh@butler.edu>, "MCCALLDON "@envelope.hp.com, HP-USA@envelope.hp.com, "MCCALL,DON (HP-USA,ex1)" <don_mccall@hp.com>, "'samba@us5.samba.org'" <samba@us5.samba.org> Subject: RE: RE: Explorer & MS Office hang Hi Nate, The interesting thing you mention is that Samba does not come down cleanly. Those smbd's that you are having to kill -9 usually indicates that the smbd is hung or spinning in some sort of loop; which would explain why you are not getting an oplock break reply from them. If you are the only one accessing the file, then the most likely senario is that the smbd that you were attached to when you opened the file got in this 'bad' state, and your pc did an autoreconnect the next time you tried to access anything on that server (which would spawn a NEW smbd). Then when you try to access the file, your NEW smbd tries to send an oplock break to the old smbd, which is hung and not replying. What we'll need to find out from the logs is WHAT the old smbd was doing right before you got your reconnection. A couple of ways to do this: in smb.conf set log file = <path>/log.%m log level = 10 debug pid = yes debug timestamp = yes This will give us a log file named log.<your client netbios machine name> the timestamp and pid debug will show us if during this problem, you end up reattaching to a different smbd, and also will let us see if the pid that the oplock message is complaining about is INDEED the previous smbd pid that you were connected to when you opened the file. These debug messages are gonna slow samba up quite a bit, so I would suggest you make a copy of your smb.conf file in the same directory with these changes, and name it smb.conf.<your client netbios machine name> and add the following line in your 'real' smb.conf file: config file = <path>/smb.conf.%m That way, only YOUR client will end up getting this high debug level, and everyone else can continue work unaffected. Let me know what you find out. hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Wednesday, March 07, 2001 11:17 AM To: "MCCALLDON "@envelope.hp.com; HP-USA@envelope.hp.com; ex1 " Subject: Re: RE: Explorer & MS Office hang Sensitivity: Confidential I'm the only one trying to access the file. It may be locked from trying to open it earlier but I'm never able to open it. We have a mixed environment with everything from win95->w2k and various versions of macOS. The only notable new thing is a win2k server. Restarting does not clear this up - in fact I have a bunch of smbd processes that won't die nicely. Usually, killing the original smbd process will kill and clean up all of them - not so anymore. It still manages most of them but about 10% aren't killed and I've terminated them with a kill -9. This seems to affect all versions of Office on both mac and pc. I even disabled my antivirus software to make sure it isn't interfering. I'll check what's logged against what's actually happening - process id's and locks - and get that to you if it will be helpful - I have some unhappy users. Thanks for your time and if this gives you any ideas plaes let me know. Nate ===========================================================From: "MCCALL,DON (HP-USA,ex1)" <don_mccall@hp.com> Date: 2001/03/07 Wed AM 09:07:27 EST To: "'npartenh@butler.edu'" <npartenh@butler.edu>, samba@us5.samba.org Subject: RE: Explorer & MS Office hang Nate, The log messages indicate that samba believes that the user being serviced by smbd with pid# 2252 has an oplock on the file, and when another client (the one that is generating this oplock break log messaga) tried to open the file, HIS smbd recognized that there was an oplock held on this file, and send an oplock break request to that pid, and never got a response. It would be interesting to know if at the time you see these messages, if the pid noted in the message shows up in a ps -ef|grep -i smb. It could indicate that this smbd process is either hung, or perhaps aborted without cleaning up it's oplocks... I haven't looked at this part of the code to determine if that is possible or not. Also, what has changed since your users have complained about this - new version of samba? new version of MS Office on the pc's? New opsys on the pc's? Does stopping and restarting samba clear this up? Hope this helps, Don -----Original Message----- From: Partenheimer Nate [mailto:npartenh@butler.edu] Sent: Wednesday, March 07, 2001 10:56 AM To: samba@lists.samba.org Subject: Explorer & MS Office hang Sensitivity: Confidential I'm running samba 2.0.7 on Solaris 2.6. We've have terrific success for well over a year with samba until about a week ago I started receiving reports that users could not open MS Office docs saved on a samba share. The samba logs are full of information about oplocks like this: [2001/03/07 10:14:04, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:08, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:27, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f [2001/03/07 10:14:29, 0] smbd/oplock.c:request_oplock_break(1204) request_oplock_break: no response received to oplock break request to pid 2252 on port 33706 for dev = 3180020, inode = 6302796 for dev = 3180020, inode = 6302796, tv_sec = 3aa6328b, tv_usec = 6168f smbstatus reports that I have an EXCLUSIVE+BATCH oplock on the file. Other documents (text, image, audio, etc) work without problems as long as they're not associated with an Office app. The office files don't seem to be corrupted either - if I ftp them to my w2k workstation I can then open them locally. I tried setting fake oplocks yes/no but that didn't seem to change anything. Any suggestions/solutions? thanks, Nate Partenheimer Information Resources Butler University npartenh@butler.edu -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba =========================================================== ============================================================