Stephen D. Williams
2001-Apr-20 17:55 UTC
Samba 2.2.0 causes Windows ME systems to lock, 2.2.0-alpha3 works fine, mostly
I have been running Samba 2.2.0-alpha3 (and alpha2 before that) for several months on SuSE 7.0 with a 2.4.2 kernel and 6+ Win98 and WindowsME workstations (and one Windows 2000 Server running in VMWare on the same server). We have been having occasional PC lockups or more commonly errors complaining about what appears to be lost connections to the server. Looking in the log file, it appears to be a problem with locking. I've tried 'Server Oplocks' on and off. The applications are shared data accounting apps that use file locking extensively. Restarting Samba, and often also the PC's, causes everything to work again. Alpha2 used to lock up all machines. Alpha3 complained about not getting a response from the client and killed just a single thread. The machine didn't recover, but other clients were ok. These messages were pretty common: [2001/04/15 18:54:25, 0] smbd/oplock.c:process_local_message(374) process_local_message: unsolicited oplock break reply from pid 26375, port 356 [2001/04/15 18:49:14, 0] smbd/oplock.c:request_oplock_break(998) request_oplock_break: no response received to oplock break request to pid 2633 for dev = 306, inode = 44442, tv_sec = 3ada4ef5, tv_usec 4485 This usually killed at least the machine involved: [2001/04/15 18:49:14, 0] smbd/oplock.c:oplock_break(763) oplock_break: end of file from client oplock_break failed for file wfx32/ctx.ini (dev = 306, inode = 28547). [2001/04/15 18:49:14, 0] smbd/oplock.c:oplock_break(854) oplock_break: client failure in break - shutting down this smbd. [2001/04/15 18:49:14, 1] smbd/service.c:close_cnum(657) rts3 (10.0.50.40) closed connection to service data Naturally I upgraded to production Samba 2.2.0. Upon first connection to the server from the WindowsME systems, they lockup and refuse to do anything else. Win98 systems seem fine. Reverting to Samba 2.2.0-alpha3 caused all machines to work again. Since I am managing this network from 6000 miles away, I'd prefer not to have to reinstall the clients. The main client is an HP 1500Mhz Pentium 4 which of course shipped with Windows ME. The server is an 800Mhz Pentium III. sdw -- sdw@lig.net http://sdw.st Stephen D. Williams 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax Dec2000 -------------- next part -------------- # Global parameters [global] workgroup = RTS netbios name = RTSLS server string = Samba 2.2.0 # server string = Samba 2.2.0-alpha3 interfaces = 10.0.50.1/255.255.255.0 10.0.50.2/255.255.255.0 encrypt passwords = Yes map to guest = Bad User unix password sync = Yes keepalive = 30 # read prediction = Yes socket options = SO_KEEPALIVE domain logons = Yes preferred master = Yes domain master = Yes wins support = Yes kernel oplocks = Yes remote announce = 10.0.50.255 socket address = 10.0.50.2/255.255.255.0 comment = Application Data, saved to tape. writeable = Yes hosts allow = 10.0.50. 216.99.99.155 192.168.1. 127.0.0.1 level2 oplocks = No path = /u/data log file = /var/log/samba/log.%m [homes] comment = Home Directories create mask = 0750 [cdr] path = /cdr [data] path = /u/data [printers] comment = All Printers path = /tmp create mask = 0700 printable = Yes browseable = No
Bill Moran
2001-Apr-21 12:38 UTC
Samba 2.2.0 causes Windows ME systems to lock, 2.2.0-alpha3 works fine, mostly
Have you tried turning oplocks off (in Samba)? That's the only way we were able to get Win 95 clients working reliably. Perhaps win ME and Win 98 have the same protocol bugs. -Bill -----Original Message----- From: Stephen D. Williams [SMTP:sdw@lig.net] Sent: Friday, April 20, 2001 1:56 PM To: samba@samba.org Subject: Samba 2.2.0 causes Windows ME systems to lock, 2.2.0-alpha3 works fine, mostly I have been running Samba 2.2.0-alpha3 (and alpha2 before that) for several months on SuSE 7.0 with a 2.4.2 kernel and 6+ Win98 and WindowsME workstations (and one Windows 2000 Server running in VMWare on the same server). We have been having occasional PC lockups or more commonly errors complaining about what appears to be lost connections to the server. Looking in the log file, it appears to be a problem with locking. I've tried 'Server Oplocks' on and off. The applications are shared data accounting apps that use file locking extensively. Restarting Samba, and often also the PC's, causes everything to work again. Alpha2 used to lock up all machines. Alpha3 complained about not getting a response from the client and killed just a single thread. The machine didn't recover, but other clients were ok. These messages were pretty common: [2001/04/15 18:54:25, 0] smbd/oplock.c:process_local_message(374) process_local_message: unsolicited oplock break reply from pid 26375, port 356 [2001/04/15 18:49:14, 0] smbd/oplock.c:request_oplock_break(998) request_oplock_break: no response received to oplock break request to pid 2633 for dev = 306, inode = 44442, tv_sec = 3ada4ef5, tv_usec 4485 This usually killed at least the machine involved: [2001/04/15 18:49:14, 0] smbd/oplock.c:oplock_break(763) oplock_break: end of file from client oplock_break failed for file wfx32/ctx.ini (dev = 306, inode = 28547). [2001/04/15 18:49:14, 0] smbd/oplock.c:oplock_break(854) oplock_break: client failure in break - shutting down this smbd. [2001/04/15 18:49:14, 1] smbd/service.c:close_cnum(657) rts3 (10.0.50.40) closed connection to service data Naturally I upgraded to production Samba 2.2.0. Upon first connection to the server from the WindowsME systems, they lockup and refuse to do anything else. Win98 systems seem fine. Reverting to Samba 2.2.0-alpha3 caused all machines to work again. Since I am managing this network from 6000 miles away, I'd prefer not to have to reinstall the clients. The main client is an HP 1500Mhz Pentium 4 which of course shipped with Windows ME. The server is an 800Mhz Pentium III. sdw -- sdw@lig.net http://sdw.st Stephen D. Williams 43392 Wayside Cir,Ashburn,VA 20147-4622 703-724-0118W 703-995-0407Fax Dec2000 << File: smb.txt >>