[Samba] Oplock problems
Dear all, I am new to this, I apologise if I am using this list improperly... I'm experiencing an oplock problem since installing windows 2000 service pack 4. The problem was not solved by upgrading from Samba 2.2.3a to 3.0.0 rc4 When I open an excel file from the windows environment no oplock is activated. This causes the problem that when I save the file I get a standard do you want to overwrite dialogue. Once the file's been saved once, the oplock kicks in EXCLUSIVE+BATCH and all is fine. (MS Word doesn't have the problem). I don't understand how oplock works, and why it's not locking the file to me as a user when I open it, but only when I save it. Can someone let me know where I might learn about oplocks or explain what the problem is so I might solve it? I've got 500 points (maybe more if it's complicated) running on this on experts exchange if anyone wants to answer it there: http://www.experts-exchange.com/Networking/Linux_Networking/Q_20749863.h tml Do I need to subscribe to the list to get an answer? Many thanks in advance, Charlie Leach -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] oplock problems with samba 2.2.7a
Hi , Before I copy and paste the oplock message(s), here is the setup I have. I have samba server (on Solaris 2.8) which shares out the NFS mounted directories to the windows world. All was working fine till today morning when users complained of extreme slow performance , looks like there is problems with oplocks accessing some files. Below is the snippet to the error log. [2003/03/24 10:26:59, 0] smbd/oplock.c:oplock_break(796) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file alt-a/fnma_delivery/April Securitization/Timeline.xls (dev = 3a8103f, inode = 133837, file_id = 159). [2003/03/24 10:26:59, 0] smbd/oplock.c:oplock_break(868) oplock_break: client failure in oplock break in file alt-a/fnma_delivery/April Securitization/Timeline.xls Any ideas to overcome the above problems?? any known issue or patch suggestions. I appreciate all inputs. Thanks in advance. Mahesh - This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please delete it and all copies from your system, destroy any hard copies and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Nomura Holding America Inc., Nomura Securities International, Inc, and their respective subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state the views of such entity. Unless otherwise stated, any pricing information in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] oplock problems
I've been using Samba mostly succesfully for my Linux box serving Win9x machines for a couple of years now In the last few days I've been getting all sorts of connectivity problems Most of the errors in the samba log files are like: [2003/02/06 09:54:16, 0] smbd/oplock.c:oplock_break(684) oplock_break: ERROR: oplock_break already sent for file docs/2002/200250/2500 Sow Unit/a1.dwg (dev = 1641, inode = 1131698, file_id = 211385) [2003/02/06 09:54:16, 0] smbd/open.c:open_mode_check(599) open_mode_check: FAILED when breaking oplock (3) on file /home/docs/2002/200250/2500 Sow Unit/a1.dwg, dev = 1641, inode = 1131698 This is what is in nmbd.log for the same time period: [2003/02/06 08:33:42, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(709) process_get_backup_list_request: domain list requested for workgroup JOHNSON and I am not a local master browser. [2003/02/06 09:51:00, 0] nmbd/nmbd_incomingdgrams.c:process_get_backup_list_request(709) process_get_backup_list_request: domain list requested for workgroup JOHNSON and I am not a local master browser. smbd.log isn't showing any errors I haven't touched the config files but I was playing with installing/using apt-get (on my Redhat server) and if I remember correctly it upgraded the samba package ... it is now: samba-client-2.2.7-1.7.3 samba-2.2.7-1.7.3 samba-common-2.2.7-1.7.3 I also switched the position of two autosensing 10/100 hubs on the network - but I don't think that would be the problem Any ideas? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
Marian, Now i am sure that this is not working(oplocks=no; veto oplock files=/*.doc/*.xls/) at all with Windows 95. No, there are none at oplocks with file locks, when oplocks=no. But, when i put oplocks=no and strict locking=yes, this seems to work(at this time, have to test more; i do not know the performance with strict locking). With these settings Excel still uses oplocks, Word approves none for oplocks. I can say this only for now, because the problems are not happening all the time only periodically. - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 21, 2002 3:01 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 OK when you use smbstatus is oplock active on open files in share with oplocks=no? - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: Marian Mlcoch, Ing [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, November 21, 2002 12:17 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, I mean that i have started from default settings and tried all off these with no help. IRIX has maintenance and feature modes for operating system. Only feature mode supports kernel oplocks and i have maintenance mode and kernel oplocks are not supported so it is same to have them off or on(on gives very many messages to log-file and this is the reason to have kernel oplocks = no at this time. I am now trying these parameters at share level(but i do not understand the difference;i will put all to defaults at global section and start with oplocks=no at share level or veto oplock files). To change oplock break wait time was an advice in web and said to help to these kind of problems with Office 97(10 is also old default allthough 0 is default for 2.2.6). We have mostly b and c versions of windows 95 and by experiment errors concerns more Windows 95b version(i do not know any service packs to go to Windows 95c at all 95 machines). - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 4:27 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 I dont understand what defaults you mean i use smaba 2.2.6 and its default is level2 oplocks = Yes kernel oplocks = Yes(this two is autodetect by samba and kernel support by samba docs IRIX have this but you have set NO???) oplock break wait time = 0(samba docs write not change this parameter...) you have level2 oplocks = no kernel oplocks = no oplock break wait time = 10 this your setings is default by your system or set in your conf file? By docs oplocks is share parameter that must by defined in share not global. best choice is try use veto oplock files= ... and leave oplocks on. And last what version of W95 you use? W95 W95a W95B ? If W95 then you must update to W95a by service pack from microsoft www. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 12:15 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, All of those are default settings and have been tested not to help. But why can i not put oplocks = no, what is standard advice with these kind of problems. Hannu - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 12:50 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Try set this level2 oplocks = Yes kernel oplocks = Yes only experimentally. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 9:34 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, Thank for You response. Here is my smb.conf: Load smb config files from /usr/samba/lib/smb.conf Processing section [homes] Processing section [printers] Processing section [nem] Processing section [ohj] Processing section [proj] Processing section [print$] Processing section [nemadmin] Loaded services file OK. # Global parameters [global] coding system = client code page = 850 code page directory = /usr/samba/lib/codepages workgroup = SAMBA netbios name = netbios aliases = netbios scope = server string = Samba
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
Hi Hannu I mean that yuor problem not is in oplock but you change from 2.0.7 to newest platform and more default values of samba conf is changed in new version. First you must post to this list your conf that is reply of samba command testparm -s afther this anybody can try help you to solve your problem. Secondary problem is compatibility of kernels that new samba is optimized for linux. Try post more information. Bye. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 15, 2002 9:37 AM Subject: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Hello, We have used Samba in SGI IRIX 6.5(now 6.5.11m) machines from the SGI version 2.0.7. We have Windows 95, NT4 and 2000 clients. We had no problems with the version 2.0.7 at all. I am looking for the new possibilities(PDC, BDC and LDAP...) with Samba 2.2.5 and newer. I installed samba.org version of Samba 2.2.5 and from that we have had problems with Office 97 documents in Windows 95 machines. Office freezes and cannot save or create new documents or open existing documents. I searched for this kind of problems from the mailing lists and the web and found out that i am not the only one having problems with oplocks. Why did i not have problems with 2.0.7, is Windows 95 support forgotten from the 2.2.x versions of Samba? The common advice is to put oplocks = no, but this i cannot do, because it means not to use Office 97 from Windows 95 machines(they cannot use any Office documents from the share or create new ones at all), why is that? Is there difference in putting oplocks =no at global or share sections on smb.conf, which kind? Is there a way of telling the client to not ask for oplocks, so that i could disable oplocks from Windows 95 machines? We are now using Samba 2.2.6 with the same problems as 2.2.5 even though there have been discussions of correcting locking problems from 2.2.5, but if this thing was fine allready in version 2.0.7, why does Samba have this kind of fundamental problems? Version 2.2.5 and 2.2.6 have oplock errors also with other programs(F-Secure Anti-Virus, AutoCAD LT 97...), but they does not seem to affect to programs like Office 97. There has been also loss of documents with Office 97 at these situations, when the program cannot save the file(anywhere anymore). I have not heard any problems with Windows NT4 or 2000 clients allthough in the web many have told there ar same kind of problems also with these clients. Hannu Virtanen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
security mode = 00 directory mask = 0755 force directory mode = 00 directory security mask = 0777 force directory security mode = 00 force unknown acl user = 00 inherit permissions = No inherit acls = No guest only = No guest ok = No only user = No hosts allow = 193.94.63. 193.66.15.38 hosts deny = status = Yes nt acl support = Yes profile acls = No block size = 1024 max connections = 0 min print space = 0 strict allocate = No strict sync = No sync always = No write cache size = 0 max print jobs = 1000 printable = No postscript = No printing = bsd print command = /usr/bsd/lpr -r -h -P%p %s lpq command = /usr/bsd/lpq -P%p lprm command = /usr/bsd/lprm -P%p %j lppause command = lpresume command = queuepause command = disable %p queueresume command = enable %p printer name = use client driver = No default devmode = No printer driver = printer driver file = /usr/samba/lib/printers.def printer driver location = default case = lower case sensitive = No preserve case = Yes short preserve case = Yes mangle case = No mangling char = ~ hide dot files = Yes hide unreadable = No delete veto files = No veto files = hide files = veto oplock files = map system = No map hidden = No map archive = Yes mangled names = Yes mangled map = browseable = Yes blocking locks = Yes csc policy = manual fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = No oplock contention limit = 2 posix locking = Yes strict locking = No share modes = Yes copy = include = exec = preexec close = No postexec = root preexec = root preexec close = No root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filemode = No dos filetimes = No dos filetime resolution = No fake directory create times = No vfs object = vfs options = [homes] comment = Home Directories valid users = hkv jyrri read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes browseable = No [nem] comment = Nemetschek Datat path = /usr/nem valid users = nykis1 jaaju kaiju terjo read only = No create mask = 0774 directory mask = 0775 [ohj] comment = Ohjelmatiedostot path = /usr/ohj valid users = +user admin users = admin hkv jyrri force group = sys read only = No [proj] comment = Projektihakemisto path = /usr/proj valid users = +user read only = No create mask = 0774 directory mask = 0775 [print$] path = /usr/samba/printer admin users = hkv write list = hkv guest ok = Yes [nemadmin] comment = Nemetschek Admin path = /usr2/nemadmin valid users = nykis1 jaaju terjo kaiju read only = No create mask = 0774 directory mask = 0775 browseable = No The Office documents are in service [proj]. Hopefully Samba is not only for Linux. Hannu - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 10:06 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Hi Hannu I mean that yuor problem not is in oplock but you change from 2.0.7 to newest platform and more default values of samba conf is changed in new version. First you must post to this list your conf that is reply of samba command testparm -s afther this anybody can try help you to solve your problem. Secondary problem is compatibility of kernels that new samba is optimized for linux. Try post more information. Bye. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 15, 2002 9:37 AM Subject: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Hello, We have used Samba in SGI IRIX 6.5(now 6.5.11m) machines from the SGI version 2.0.7. We have Windows 95, NT4 and 2000 clients. We had no problems with the version 2.0.7 at all. I am looking for the new
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
Try set this level2 oplocks = Yes kernel oplocks = Yes only experimentally. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 9:34 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, Thank for You response. Here is my smb.conf: Load smb config files from /usr/samba/lib/smb.conf Processing section [homes] Processing section [printers] Processing section [nem] Processing section [ohj] Processing section [proj] Processing section [print$] Processing section [nemadmin] Loaded services file OK. # Global parameters [global] coding system = client code page = 850 code page directory = /usr/samba/lib/codepages workgroup = SAMBA netbios name = netbios aliases = netbios scope = server string = Samba 2.2.6 interfaces = bind interfaces only = No security = USER encrypt passwords = Yes update encrypted = No allow trusted domains = Yes hosts equiv = min passwd length = 5 map to guest = Never null passwords = No obey pam restrictions = No password server = smb passwd file = /usr/samba/private/smbpasswd root directory = pam password change = No passwd program = /usr/bin/passwd %u passwd chat = *ew*password:* %n\n *e-enter*new*password:* %n\n passwd chat debug = No username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = No lanman auth = Yes use rhosts = No admin log = No log level = 0 syslog = 1 syslog only = No log file = max log size = 50 timestamp logs = Yes debug hires timestamp = No debug pid = No debug uid = No protocol = NT1 large readwrite = Yes max protocol = NT1 min protocol = CORE read bmpx = No read raw = Yes write raw = Yes nt smb support = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = lmhosts host wins bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = No unix extensions = No change notify timeout = 60 deadtime = 15 getwd cache = Yes keepalive = 300 lpq cache time = 10 max smbd processes = 0 max disk size = 0 max open files = 1 name cache timeout = 660 read size = 16384 socket options = TCP_NODELAY stat cache size = 50 use mmap = Yes total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = strip dot = No mangling method = hash character set = mangled stack = 50 stat cache = Yes domain admin group = domain guest group = machine password timeout = 604800 add user script = delete user script = logon script = logon path = \\%N\%U\profile logon drive = logon home = \\%N\%U domain logons = No os level = 65 lm announce = Auto lm interval = 60 preferred master = Yes local master = Yes domain master = Yes browse list = Yes enhanced browsing = Yes dns proxy = Yes wins proxy = No wins server = wins support = Yes wins hook = kernel oplocks = No lock spin count = 3 lock spin time = 10 oplock break wait time = 10 add share command = change share command = delete share command = config file = preload = lock dir = /usr/samba/var/locks pid directory = /usr/samba/var/locks default service = message command = dfree command = valid chars = remote announce = remote browse sync = socket address = 0.0.0.0 homedir map = time offset = 0 NIS homedir = No source environment = panic action = hide local users = No winbind uid = winbind gid = template homedir = /home/%D/%U template shell = /bin/false winbind separator = \ winbind cache time = 15 winbind enum users = Yes winbind enum groups = Yes winbind use
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
Marian, All of those are default settings and have been tested not to help. But why can i not put oplocks = no, what is standard advice with these kind of problems. Hannu - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 12:50 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Try set this level2 oplocks = Yes kernel oplocks = Yes only experimentally. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 9:34 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, Thank for You response. Here is my smb.conf: Load smb config files from /usr/samba/lib/smb.conf Processing section [homes] Processing section [printers] Processing section [nem] Processing section [ohj] Processing section [proj] Processing section [print$] Processing section [nemadmin] Loaded services file OK. # Global parameters [global] coding system = client code page = 850 code page directory = /usr/samba/lib/codepages workgroup = SAMBA netbios name = netbios aliases = netbios scope = server string = Samba 2.2.6 interfaces = bind interfaces only = No security = USER encrypt passwords = Yes update encrypted = No allow trusted domains = Yes hosts equiv = min passwd length = 5 map to guest = Never null passwords = No obey pam restrictions = No password server = smb passwd file = /usr/samba/private/smbpasswd root directory = pam password change = No passwd program = /usr/bin/passwd %u passwd chat = *ew*password:* %n\n *e-enter*new*password:* %n\n passwd chat debug = No username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = No lanman auth = Yes use rhosts = No admin log = No log level = 0 syslog = 1 syslog only = No log file = max log size = 50 timestamp logs = Yes debug hires timestamp = No debug pid = No debug uid = No protocol = NT1 large readwrite = Yes max protocol = NT1 min protocol = CORE read bmpx = No read raw = Yes write raw = Yes nt smb support = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = lmhosts host wins bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = No unix extensions = No change notify timeout = 60 deadtime = 15 getwd cache = Yes keepalive = 300 lpq cache time = 10 max smbd processes = 0 max disk size = 0 max open files = 1 name cache timeout = 660 read size = 16384 socket options = TCP_NODELAY stat cache size = 50 use mmap = Yes total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = strip dot = No mangling method = hash character set = mangled stack = 50 stat cache = Yes domain admin group = domain guest group = machine password timeout = 604800 add user script = delete user script = logon script = logon path = \\%N\%U\profile logon drive = logon home = \\%N\%U domain logons = No os level = 65 lm announce = Auto lm interval = 60 preferred master = Yes local master = Yes domain master = Yes browse list = Yes enhanced browsing = Yes dns proxy = Yes wins proxy = No wins server = wins support = Yes wins hook = kernel oplocks = No lock spin count = 3 lock spin time = 10 oplock break wait time = 10 add share command = change share command = delete share command = config file = preload = lock dir = /usr/samba/var/locks pid directory = /usr/samba/var/locks default service = message
Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
I dont understand what defaults you mean i use smaba 2.2.6 and its default is level2 oplocks = Yes kernel oplocks = Yes(this two is autodetect by samba and kernel support by samba docs IRIX have this but you have set NO???) oplock break wait time = 0(samba docs write not change this parameter...) you have level2 oplocks = no kernel oplocks = no oplock break wait time = 10 this your setings is default by your system or set in your conf file? By docs oplocks is share parameter that must by defined in share not global. best choice is try use veto oplock files= ... and leave oplocks on. And last what version of W95 you use? W95 W95a W95B ? If W95 then you must update to W95a by service pack from microsoft www. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 12:15 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, All of those are default settings and have been tested not to help. But why can i not put oplocks = no, what is standard advice with these kind of problems. Hannu - Original Message - From: Marian Mlcoch, Ing [EMAIL PROTECTED] To: Hannu Virtanen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 12:50 PM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Try set this level2 oplocks = Yes kernel oplocks = Yes only experimentally. - Original Message - From: Hannu Virtanen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 18, 2002 9:34 AM Subject: Re: [Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7 Marian, Thank for You response. Here is my smb.conf: Load smb config files from /usr/samba/lib/smb.conf Processing section [homes] Processing section [printers] Processing section [nem] Processing section [ohj] Processing section [proj] Processing section [print$] Processing section [nemadmin] Loaded services file OK. # Global parameters [global] coding system = client code page = 850 code page directory = /usr/samba/lib/codepages workgroup = SAMBA netbios name = netbios aliases = netbios scope = server string = Samba 2.2.6 interfaces = bind interfaces only = No security = USER encrypt passwords = Yes update encrypted = No allow trusted domains = Yes hosts equiv = min passwd length = 5 map to guest = Never null passwords = No obey pam restrictions = No password server = smb passwd file = /usr/samba/private/smbpasswd root directory = pam password change = No passwd program = /usr/bin/passwd %u passwd chat = *ew*password:* %n\n *e-enter*new*password:* %n\n passwd chat debug = No username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = No lanman auth = Yes use rhosts = No admin log = No log level = 0 syslog = 1 syslog only = No log file = max log size = 50 timestamp logs = Yes debug hires timestamp = No debug pid = No debug uid = No protocol = NT1 large readwrite = Yes max protocol = NT1 min protocol = CORE read bmpx = No read raw = Yes write raw = Yes nt smb support = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = lmhosts host wins bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = No unix extensions = No change notify timeout = 60 deadtime = 15 getwd cache = Yes keepalive = 300 lpq cache time = 10 max smbd processes = 0 max disk size = 0 max open files = 1 name cache timeout = 660 read size = 16384 socket options = TCP_NODELAY stat cache size = 50 use mmap = Yes total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = strip dot = No mangling method = hash character set = mangled stack = 50 stat cache = Yes
[Samba] Oplock problems with Office 97 and Windows 95 in Samba 2.0.7
Hello, We have used Samba in SGI IRIX 6.5(now 6.5.11m) machines from the SGI version 2.0.7. We have Windows 95, NT4 and 2000 clients. We had no problems with the version 2.0.7 at all. I am looking for the new possibilities(PDC, BDC and LDAP...) with Samba 2.2.5 and newer. I installed samba.org version of Samba 2.2.5 and from that we have had problems with Office 97 documents in Windows 95 machines. Office freezes and cannot save or create new documents or open existing documents. I searched for this kind of problems from the mailing lists and the web and found out that i am not the only one having problems with oplocks. Why did i not have problems with 2.0.7, is Windows 95 support forgotten from the 2.2.x versions of Samba? The common advice is to put oplocks = no, but this i cannot do, because it means not to use Office 97 from Windows 95 machines(they cannot use any Office documents from the share or create new ones at all), why is that? Is there difference in putting oplocks =no at global or share sections on smb.conf, which kind? Is there a way of telling the client to not ask for oplocks, so that i could disable oplocks from Windows 95 machines? We are now using Samba 2.2.6 with the same problems as 2.2.5 even though there have been discussions of correcting locking problems from 2.2.5, but if this thing was fine allready in version 2.0.7, why does Samba have this kind of fundamental problems? Version 2.2.5 and 2.2.6 have oplock errors also with other programs(F-Secure Anti-Virus, AutoCAD LT 97...), but they does not seem to affect to programs like Office 97. There has been also loss of documents with Office 97 at these situations, when the program cannot save the file(anywhere anymore). I have not heard any problems with Windows NT4 or 2000 clients allthough in the web many have told there ar same kind of problems also with these clients. Hannu Virtanen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] oplock problems
Eddy, As you have noticed, there is currently no fix (please correct me if I'm wrong) for the oplock problems you're experiencing. the oplock errors are definitely related the performance problems your customers are complaining about. oplocks are 'opportunistic locks' in which the client machine already has the file locked and all changes are made in a cached copy of the file on the client. When oplocks work correctly, the client periodically flushes the locally cached copy of the data file back to the server. When they don't work correctly, the kind of errors that you and your customers are noticing occur. The following is an exerpt from a message posted here by Mr. Jeremy Allison, a key member of the samba development production team: Also, something Jeremy posted to the list a few days ago: Ok, as promised, a brief explaination of oplocks, share modes and locking. When a client opens a file it can request an oplock or file lease. This is (to simplify a bit) a guarentee that no one else has the file open simultaneously. It allows the client to not send any updates on the file to the server, thus reducing a network file access to local access (once the file is in client cache). An oplock break is when the server sends a request to the client to flush all its changes back to the server, so the file is in a consistent state for other opens to succeed. If a client fails to respond to this asynchronous request then the file can be corrupted. Hence the turn off oplocks answer if people are having multi-user file access problems. Unless the kernel is oplock aware (SGI IRIX and Linux are the only two UNIXes that are at the moment) then if a local UNIX process accesses the file simultaneously then Samba has no way of telling this is occuring, so the guarentee to the client is broken. This can corrupt the file. Short answer - it you have UNIX clients accessing the same file as smbd locally or via NFS and you're not running Linux or IRIX then turn off oplocks for that file or share. Share modes. These are modes of opening a file, that guarentee an invarient - such as DENY_WRITE - which means that if any other opens are requested with write access after this current open has succeeded then they should be denied with a sharing violation error message. Samba handles these internally inside smbd. UNIX clients accessing the same file ignore these invarients. Just proving that if you need simultaneous file access from a Windows and UNIX client you *must* have an application that is written to lock records correctly on both sides. Few applications are written like this, and even fewer are cross platform (UNIX and Windows) so in practice this isn't much of a problem. Locking. This really means byte range locking - such as lock 10 bytes at file offset 24 for write access. This is the area in which well written UNIX and Windows apps will cooperate. Windows locks (at least from NT or above) are 64-bit unsigned offsets. UNIX locks are either 31 bit or 63 bit and are signed (the top bit is used for the sign). Samba handles these by first ensuring that all the Windows locks don't conflict (ie. if other Windows clients have competing locks then just reject immediately) - this allows us to support 64-bit Windows locks on 32-bit filesystems. Secondly any locks that are valid are then mapped onto UNIX fcntl byte range locks. These are the locks that will be seen by UNIX processes. If there is a conflict here the lock is rejected. Note that if a client has an oplock then it knows that no other client can have the file open so usually doesn't bother to send to lock request to the server - this means once again if you need to share files between UNIX and Windows processes either use IRIX or Linux, or turn off oplocks for these files/shares. Hope this is clear :-). Jeremy. At 04:34 PM 10/29/2002 +0100, [EMAIL PROTECTED] wrote: We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11 fileservers. Our customers are complaining about slow response on the opening/closing of files in office/excel etc. In the samba log file we see the following messages : [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file My Documents/servers.doc (dev = 40220001, inode = 229991, file_id = 240). [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(833) oplock_break: client failure in oplock break in file My Documents/servers.doc [2002/10/29 09:03:27, 0] ../source/smbd/reply.c:(4387) reply_lockingX: Error : oplock break from client for fnum = 14026 and no oploc k granted on this file (My Documents/servers.doc). We found out that these messages correspond with the slow response that our users are seeing. I've searched the samba archive and there are more people having these messages. The solutions I found were : - You may have a netwerk problem ( which is NOT the case in our situation ) - Turn oplocks off ( But this
Re: [Samba] oplock problems
Eddy, One more thing, I have anecdotal evidence (not emperical) that we've had fewer oplock problems with our computers that are configured to use the samba server as their Domain Controller. Obviously, there is some administrative over head involved with that. If you are able to run some experiments, I'd appreciate some feedback about what worked best for you. --- Sam Barasch Computer Systems Support Department of Biostatistics University of Wisconsin Madison -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] oplock problems
A full explanation of oplocks from Jeremy below. The basic rule seems to be if a file is static data being shared to many people then oplocks will increase performace. If you are dishing out Office documents you had best turn oplocks off totally. Oplocks = no Kernel Oplocks = no Level2 Oplocks = no hth Noel Ok, as promised, a brief explaination of oplocks, share modes and locking. When a client opens a file it can request an oplock or file lease. This is (to simplify a bit) a guarentee that no one else has the file open simultaneously. It allows the client to not send any updates on the file to the server, thus reducing a network file access to local access (once the file is in client cache). An oplock break is when the server sends a request to the client to flush all its changes back to the server, so the file is in a consistent state for other opens to succeed. If a client fails to respond to this asynchronous request then the file can be corrupted. Hence the turn off oplocks answer if people are having multi-user file access problems. Unless the kernel is oplock aware (SGI IRIX and Linux are the only two UNIXes that are at the moment) then if a local UNIX process accesses the file simultaneously then Samba has no way of telling this is occuring, so the guarentee to the client is broken. This can corrupt the file. Short answer - it you have UNIX clients accessing the same file as smbd locally or via NFS and you're not running Linux or IRIX then turn off oplocks for that file or share. Share modes. These are modes of opening a file, that guarentee an invarient - such as DENY_WRITE - which means that if any other opens are requested with write access after this current open has succeeded then they should be denied with a sharing violation error message. Samba handles these internally inside smbd. UNIX clients accessing the same file ignore these invarients. Just proving that if you need simultaneous file access from a Windows and UNIX client you *must* have an application that is written to lock records correctly on both sides. Few applications are written like this, and even fewer are cross platform (UNIX and Windows) so in practice this isn't much of a problem. Locking. This really means byte range locking - such as lock 10 bytes at file offset 24 for write access. This is the area in which well written UNIX and Windows apps will cooperate. Windows locks (at least from NT or above) are 64-bit unsigned offsets. UNIX locks are either 31 bit or 63 bit and are signed (the top bit is used for the sign). Samba handles these by first ensuring that all the Windows locks don't conflict (ie. if other Windows clients have competing locks then just reject immediately) - this allows us to support 64-bit Windows locks on 32-bit filesystems. Secondly any locks that are valid are then mapped onto UNIX fcntl byte range locks. These are the locks that will be seen by UNIX processes. If there is a conflict here the lock is rejected. Note that if a client has an oplock then it knows that no other client can have the file open so usually doesn't bother to send to lock request to the server - this means once again if you need to share files between UNIX and Windows processes either use IRIX or Linux, or turn off oplocks for these files/shares. Hope this is clear :-). Jeremy. -Original Message- From: [EMAIL PROTECTED] [mailto:c.m.e.reniers;philips.com] Sent: 29 October 2002 15:35 To: [EMAIL PROTECTED] Subject: [Samba] oplock problems We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11 fileservers. Our customers are complaining about slow response on the opening/closing of files in office/excel etc. In the samba log file we see the following messages : [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file My Documents/servers.doc (dev = 40220001, inode = 229991, file_id = 240). [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(833) oplock_break: client failure in oplock break in file My Documents/servers.doc [2002/10/29 09:03:27, 0] ../source/smbd/reply.c:(4387) reply_lockingX: Error : oplock break from client for fnum = 14026 and no oploc k granted on this file (My Documents/servers.doc). We found out that these messages correspond with the slow response that our users are seeing. I've searched the samba archive and there are more people having these messages. The solutions I found were : - You may have a netwerk problem ( which is NOT the case in our situation ) - Turn oplocks off ( But this may introduce a performance problem ) Can somebody please explain : - What this message really means. - Can it be related to the slow response that our customers are complaining about - Is there a solution to this probem ( our network is ok, turning oplocks off is not a solution .. ) Regards, Eddy Reniers, Philips Research Laboratories Department Computer Services
