Hi again Volker (& list)
I think I am very closer of the problem.
Look at this please
# A file is deleted => OK
[2015/03/06 07:31:45.359108, 2]
smbd/open.c:704(open_file) expl opened file
PRENSA_Avance1_20150306_070500.pdf read=No write=No (numopen=1)
[2015/03/06 07:31:45.359145, 5]
smbd/oplock.c:92(set_file_oplock) set_file_oplock: granted
oplock on file PRENSA_Avance1_20150306_070500.pdf,
30c0fc03:19d62:0/422320395, tv_sec = 54f949d1, tv_usec = 57a9d
[2015/03/06 07:31:45.360811, 2]
smbd/close.c:696(close_normal_file) expl closed file
PRENSA_Avance1_20150306_070500.pdf (numopen=0) NT_STATUS_OK
# Another file is opened for writting
[2015/03/06 07:31:46.489776, 2]
smbd/open.c:704(open_file) expl opened file
PRENSA_Avance1_20150306_073144.pdf read=Yes write=Yes (numopen=1)
# 73 seconds later without any information, the connection is closed by
samba side (global smb.conf section)
[2015/03/06 07:32:59.089671, 2]
smbd/sesssetup.c:1279(setup_new_vc_session) setup_new_vc_session:
New VC == 0, if NT4.x compatible we would close all old
resources.
[2015/03/06 07:32:59.089731, 1]
smbd/sesssetup.c:1269(shutdown_other_smbds) shutdown_other_smbds:
shutting down pid 61148 (IP 172.30.35.65)
[2015/03/06 07:32:59.090343, 1]
smbd/sesssetup.c:1269(shutdown_other_smbds) shutdown_other_smbds:
shutting down pid 61148 (IP
172.30.35.65)
# Finally the granted oplock came but it was too late
[2015/03/06 07:32:59.090345, 5]
smbd/oplock.c:92(set_file_oplock) set_file_oplock: granted
oplock on file PRENSA_Avance1_20150306_073144.pdf,
30c0fc03:169b7:0/422320396, tv_sec = 54f949d2, tv_usec = 77816
[2015/03/06 07:32:59.090598, 1] smbd/process.c:167(srv_send_smb)
Here it is the [global section] is in place
[global]
log file = /var/log/samba/log.%m
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=16384
SO_SNDBUF=16384 SO_KEEPALIVE TCP_KEEPIDLE=100 TCP_KEEPINTVL=10 TCP_KEEPCNT=5
encrypt passwords = true
wins support = true
nt acl support = Yes
logon script = %U.bat
local master = yes
workgroup = SMBBD
name resolve order = bcast host
server string = Servidor Samba NOCON
security = share
map to guest = Bad User
preferred master = yes
bind interfaces only = True
max log size = 50
domain logons = Yes
smb ports=139
log level = 2 locking:5
deadtime = 2
reset on zero vc = yes
locking = Yes
strict locking = No
posix locking = No
oplocks = no
level2 oplocks = No
fake oplocks = No
blocking locks = Yes
I think the oplock is waiting a response from the file system for granting
the locking over the file, is it true?
If so, should I set 'locking = no' in the global section
Thanks for your help
PS: I have been reading oplock.c but I don't know from where it is called
2015-02-11 12:05 GMT+01:00 Volker Lendecke <Volker.Lendecke at sernet.de>:
> On Wed, Feb 11, 2015 at 12:01:34PM +0100, Nacho del Rey wrote:
> > The symptom is that the windows process which is accessing the samba
> share
> > hangs
> > Also, if you try to open the same share (you can do the connection) to
> see
> > the files, the ls command hangs
> >
> > The other samba shares don't be affected at all, they work ok
> >
> > So the only thing you can do is a reload/restart to resume operations
>
> To be honest, in such a case I think it would be best for you to contact
> someone from https://www.samba.org/samba/support/ to log into your system
> and really nail down what happens. This can best be solved with direct
> access to the system, something you don't want to let someone do
without
> a contract and NDA.
>
> Volker
>
> --
> SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen
> http://www.sernet.de, mailto:kontakt at sernet.de
>