samba - Aug 2005 - Samba 3.0.20 on Solaris: problem with fileaccess in a automounted filesystem

Regards,

Sent this one before, here's another go:

My sambaserver, let's call it sserv, is running Solaris 8 (latest 
Recommended set) or 9 (tried both) compiled with automount support.
When PC client A tries to access a file in a automounted mapping from 
sserv, the client is freezing and Windows Explorer has to be restarted.
The NFS server which the samba server automounts from is a Solaris 2.5.1 
system.
The strange thing is that the same scenario works OK when the samba 
server is an Sgi IRIX system. The following pops up in the log for PC 
client A on sserv:

[2005/08/26 15:57:29, 0] smbd/oplock.c:(1081)
   request_oplock_break: no response received to oplock break request to 
pid 16838 on port 58990 for dev = 4f4001d, inode = 187327, file_id = 51
[2005/08/26 15:57:29, 0] smbd/open.c:(726)
   open_mode_check: exlusive oplock left by process 16838 after break ! 
For file test.zip, dev = 4f4001d, inode = 187327. Deleting it to continue...

Someone's got a clue ?
-- 

       ******************************************************************
       *         Knut Helleb?                     | DAMN GOOD COFFEE !! *
       * Hydro IS Partner ESI (Unix) Team         | (and hot too)       *
       *                                          |                     *
       * E-mail: Knut.Hellebo@nho.hydro.com       | Dale Cooper, FBI    *
       ******************************************************************

-------------- next part --------------


***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************

tom@ee.ucl.ac.uk wrote:
> Hello Knut,
> 
> The problem may well be related to locking problems between the samba
> server and the NFS server (Solaris 2.5.1). Isn't 2.5.1 unsupported now?
> Have you patched it up as much as you can?
> 
Yes, so I have been thinking myself, but when logging on to the Solaris 
samba server which mounts from the 2.5.1 nfs server, checking/accessing 
the files/directories seems fine. No locking problems. Also, when using 
a Sgi samba server mounting from the same Solaris 2.5.1 system, 
everything is fine. One should think that it is more likely that things 
would work better between two Sun boxes than between a Sun and a Sgi. I 
will try to patch the Solaris 2.5.1 server with the latest recommended 
set and see if this helps.
-- 

       ******************************************************************
       *         Knut Helleb?                     | DAMN GOOD COFFEE !! *
       * Hydro IS Partner ESI (Unix) Team         | (and hot too)       *
       *                                          |                     *
       * E-mail: Knut.Hellebo@nho.hydro.com       | Dale Cooper, FBI    *
       ******************************************************************

-------------- next part --------------


***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************