SAMBA digest 1563

[Matthew Geier]

> From: Panu Outinen <panu at vertex.vertex.fi>
> To: samba at samba.anu.edu.au
> Subject: Major problems with Samba 1.9.18p1 (HPUX 9.05) with oplocks
> Message-ID: <3.0.1.32.19980120192818.009ff290 at vertex.fi>
> 
> Hi there!
> 
> I'm having major problems with the new oplocks feature of Samba 1.9.18p1.
> After running about a day or more Samba processes seem to stop responding
> or programs say that they can't open files that do exist and have been

> 01/20/1998 14:53:37 nicklaus (192.4.0.177) connect to service all as user
> vertex (uid=201,gid=20) (pid 20019)
> 01/20/1998 14:53:53 request_oplock_break: no response received to oplock
> break request to pid 19758 on port 1523 for dev = 7201600, inode = 2b58c
> 01/20/1998 14:54:01 sirpa (192.4.0.60) connect to service all as user
> vertex (uid=201,gid=20) (pid 20025)
> 01/20/1998 14:54:25 request_oplock_break: no response received to oplock
> break request to pid 19758 on port 1523 for dev = 7201600, inode = 2b58c
> 01/20/1998 14:54:33 request_oplock_break: no response received to oplock
> break request to pid 19758 on port 1523 for dev = 7201600, inode = 2b595

 Ive actually had this happen with 1.9.18 with us. A random user managed
to spawn lots of connections, and samba got into a knot with locking.
 The client kept reconnecting untill our server ran out of memory. After
killing off ALL the smbd processes belonging to that user, all worked
fine again. I dont think it has happened to us under 18p1. It happened
about 3 times uner 18p0.



-- 
Matthew Geier,                          matthew at law.usyd.edu.au
Computer Systems Manager,               +61 2 9351 0240
Law School, University of Sydney        +61 2 9351 0200 (fax)