Hi Volker and the list
Yesterday the problem appeared again
I could launch a strace command over a samba PID to see what was going on
and this is the result
[PRO] [root at pf3il0024 ~]# strace -frp 57686
Process 57686 attached - interrupt to quit
0.000000 fcntl(14, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET,
start=35824, len=1}
It seems the process was trying to get a read-lock but no one answers
I don't know where to find out more information about this issue
Any other clues?
Thanks in advance
Nacho.
I attach a smbstatus command execution:
Service pid machine Connected at
-------------------------------------------------------
mofis 32789 n1414 Mon Feb 9 18:04:02 2015
mofis 50938 n1414 Mon Feb 9 18:08:22 2015
mofis 50938 n1414 Mon Feb 9 18:08:21 2015
mofis 21976 pv0il0231.cc0.m Sun Feb 1 01:35:01 2015
IPC$ 50938 n1414 Mon Feb 9 18:08:22 2015
dossiers 65440 op790-2qmx55j Tue Feb 10 10:13:43 2015
dossiers 57686 op790-7g2x55j Tue Feb 10 10:10:59 2015
IPC$ 32789 n1414 Mon Feb 9 18:06:50 2015
siext 29617 pv0iw0054 Mon Feb 9 06:43:56 2015
mofis 17853 n1414 Mon Feb 9 21:04:52 2015
siext 43962 pv0iw0054 Mon Feb 9 06:48:22 2015
mofis 28386 n1414 Mon Feb 9 18:01:48 2015
siext 49128 pv0iw0054 Mon Feb 9 06:49:53 2015
dossiers 58388 op790-2qmx55j Tue Feb 10 10:11:10 2015
dossiers 64839 op790-7g2x55j Tue Feb 10 10:13:30 2015
IPC$ 24790 n1414 Mon Feb 9 18:00:27 2015
siext 38701 pv0iw0054 Mon Feb 9 06:46:51 2015
IPC$ 29617 pv0iw0054 Mon Feb 9 06:43:56 2015
siext 34458 pv0iw0054 Mon Feb 9 06:45:20 2015
mofis 21975 pv0il0230.cc0.m Sun Feb 1 01:35:00 2015
dossiers 50803 pv0iw0053 Tue Feb 10 10:08:50 2015
mofis 24790 n1414 Mon Feb 9 18:00:33 2015
mofis 32789 n1414 Mon Feb 9 18:03:18 2015
dossiers 61997 op790-7g2x55j Tue Feb 10 10:12:27 2015
siext 53030 pv0iw0054 Mon Feb 9 06:51:24 2015
Locked files:
Pid Uid DenyMode Access R/W Oplock
SharePath Name Time
--------------------------------------------------------------------------------------------------
24790 504 DENY_NONE 0x100081 RDONLY NONE
/opt/srv007/app/mofis/datos . Mon Feb 9 18:00:34 2015
57686 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:10:59 2015
57686 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:10:59 2015
57686 504 DENY_NONE 0x100081 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:10:59 2015
58388 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:11:10 2015
58388 504 DENY_NONE 0x100081 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:11:10 2015
61997 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/publi/datos/dossiers . Tue Feb 10 10:12:28 2015
24790 504 DENY_NONE 0x100081 RDONLY NONE
/opt/srv007/app/mofis/datos salida Mon Feb 9 18:00:34 2015
24790 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/mofis/datos historico Mon Feb 9 18:00:34 2015
28386 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/mofis/datos historico Mon Feb 9 18:01:48 2015
32789 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/mofis/datos historico Mon Feb 9 18:06:54 2015
50938 504 DENY_NONE 0x81 RDONLY NONE
/opt/srv007/app/mofis/datos historico Mon Feb 9 18:08:27 20
2014-12-31 9:44 GMT+01:00 Nacho del Rey <odelreym at gmail.com>:
> Hi Volker
>
> Finally I loaded the following configuration in our test environment
>
> [global]
>
> deadtime = 60
>
> keepalive = 10
>
>
> [dossiers]
>
>
> locking = Yes
>
> ; If yes, turns on byte-range locks.
>
> strict locking = No
>
> ; If yes, denies access to an entire file if a byte-range lock
> exists in it.
>
> ; posix locking = Yes
>
> posix locking = No
>
> ; If yes, maps oplocks to POSIX locks on the local system.
>
> oplocks = no
>
> ; If yes, turns on local caching of files on the client for this
> share.
>
> level2 oplocks = No
>
> ; If yes, allows oplocks to downgrade to read-only.
>
> fake oplocks = No
>
> ; If yes, tells client the lock was obtained, but doesn't
actually
> lock it.
>
> blocking locks = Yes
>
> ; Allows lock requestor to wait for the lock to be granted.
>
> I have been reading a lot about samba & win7 and it is probably we have
> another issue when the windows clients enter in hibernating mode, so the
> parameters deadtime & keepalive in global section
>
> Yesterday we did a bunch of tests and, for the moment, it seems to run
> properly
>
> Thanks for your clue
> I will update this issue as soon as I will confirm the solution is
> permanent
>
> Kind regards and have a happy new year
>
> Nacho.
>
>
>
>
>
>
>
> 2014-12-17 8:48 GMT+01:00 Nacho del Rey <odelreym at gmail.com>:
>
>>
>>> > >Please remove the SO_RCVBUF and SO_SNDBUF entries.
>>> > >Oh, that's ancient. Do you have any possibility to
move to
>>> > >"security=user"?
>>> > The smb.conf file was inherited from HP-UX
system. Ok,
>>> > I'll remove them
>>> >
>>> > >Did you try "posix locking = no"? That is mostly
criticial
>>> > >if you are exporting files from a file system with
>>> > >unreliable locking like for example NFS.
>>> >
>>> > There is no NFS at all over the fs. It is only ACFS
+ samba.
>>> We
>>> > tried to disable any interference with posix locks over the
ACFS, so
>>> the
>>> > parameter was set to no. Is it right?
>>>
>>> In your smb.conf, it was set to yes, that's why I was
>>> asking. Setting "posix locking = no" is the right thing
to
>>> do in this case. I mentioned NFS just as an example of a
>>> file system where locking can be problematic. It sounds like
>>> ACFS also could have problems here, thus the analogy.
>>>
>>> Ah, ok. I did not understand you properly. We'll try this
change
>>
>>
>>> >
>>> > >Can you see what the smbd hosting such a blocked client
does?
>>> > >If it is in D state (according to ps u), it sits in the
>>> > >kernel. If not, you could try stracing the process (strace
>>> > >-ttT -p <pid>) and see what it does. gstack
<pid> also helps
>>> > >often.
>>> >
>>> > We got the following strace over the samba process
'locked'
>>>
>>> The strace looks innocent. Have you been able to see what
>>> state the process was in while the client was blocked?
>>>
>>>
>> I will ask for it to my workmates if they can have it one 'top'
capture
>> (I don't think so)
>>
>> I'll come back to you as soon as I get the results
>>
>> Many thanks Volker
>>
>> Nacho
>>
>>
>>
>