samba - May 2020 - 4.12.2 breaks with win clients NT_STATUS_SHARING_VIOLATION

Hi
After Fedora 31 upgrade to F32, samba started to break after more 
clients connect (up to 10).
No config change, no clients change, no sharing changes.? F31 had smb 
4.11.7 and was working fine
after restarting service it works for a while then it breaks with 
various messages for each client

I tried removing some old parameters (no help), I had mounted ssd drive 
into folder structure and I removed it, I did complete uninstall and 
remove all samba related files from /usr/lib64/samba, /var/run/samba, 
/var/log/samba, /usr/share/samba, and maybe some more
It seems quite clean install.? Based on the messages it seems that at 
certain amount of files open, it will break.? I have same F32 with samba 
sharing on different servers with only a few clients, and it doesn't 
break any more after update from 4.12.1, but it's also very little load

#testparm
-------------------------------------------------------------------------------------
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
 ??????? bind interfaces only = Yes
 ??????? dns proxy = No
 ??????? domain master = Yes
 ??????? enumports command = /etc/samba/ports
 ??????? interfaces = em1 lo
 ??????? log file = /var/log/samba/log.%m
 ??????? max log size = 2500
 ??????? message command = csh -c ?xedit %s;rm %s? &
 ??????? name resolve order = lmhosts wins bcast
 ??????? os level = 88
 ??????? passdb backend = tdbsam:/etc/samba/tsmbpass.tdb
 ??????? preferred master = Yes
 ??????? printcap name = cups
 ??????? remote announce = 192.168.3.255/GROUP
 ??????? security = USER
 ??????? server string = cfl server
 ??????? unix charset = UTF8
 ??????? username map = /etc/samba/smbusers
 ??????? wins support = Yes
 ??????? workgroup = FIRMA
 ??????? idmap config * : backend = tdb
 ??????? case sensitive = No
 ??????? hosts allow = 192.168. 127.

[homes]
 ??????? browseable = No
 ??????? comment = Home Directories
 ??????? read only = No

[arhiv]
 ??????? comment = Arhiv
 ??????? invalid users = nobody
 ??????? path = /1-Arhiv
 ??????? read only = No

[posl-prog]
 ??????? comment = Programi
 ??????? create mask = 0777
 ??????? force create mode = 0777
 ??????? force directory mode = 0777
 ??????? guest ok = Yes
 ??????? invalid users = nobody
 ??????? path = /data/1-Program
 ??????? read only = No
--------------------------------------------------------------------------------------
messages from log files
------------------------------------------------------------------------------------
[2020/05/11 08:33:52.049764,? 3] 
../../source3/smbd/smb2_server.c:3272(smbd_smb2_request_error_ex)
 ? smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_INVALID_DEVICE_REQUEST] || at 
../../source3/smbd/smb2_ioctl.c:312
[2020/05/11 08:33:52.057652,? 3] 
../../source3/smbd/smb2_server.c:3272(smbd_smb2_request_error_ex)
 ? smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_ACCESS_DENIED] || at ../../source3/smbd/smb2_tcon.c:142
[2020/05/11 08:19:00.072196,? 3] 
../../source3/smbd/smb2_server.c:3272(smbd_smb2_request_error_ex)
 ? smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_SHARING_VIOLATION] || at 
../../source3/smbd/smb2_create.c:334
[2020/05/11 08:33:47.156000,? 3] 
../../source3/smbd/smb2_server.c:3272(smbd_smb2_request_error_ex)
 ? smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] 
status[NT_STATUS_OBJECT_NAME_NOT_FOUND] || at 
../../source3/smbd/smb2_create.c:334
----------------------------------------------------------------------------------


Regards
Denis

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Am 5/11/20 um 8:45 AM schrieb Denis via samba:
> Hi
> After Fedora 31 upgrade to F32, samba started to break after more
> clients connect (up to 10).
> No config change, no clients change, no sharing changes.? F31 had smb
> 4.11.7 and was working fine
> after restarting service it works for a while then it breaks with
> various messages for each client
this is probably

https://bugzilla.samba.org/show_bug.cgi?id=14375

which I just created for an issue I tracked down on this weekend.

A fix will ship with the next release.

-slow

-- 
Ralph Boehme, Samba Team                https://samba.org/
Samba Developer, SerNet GmbH   https://sernet.de/en/samba/
GPG-Fingerprint   FAE2C6088A24252051C559E4AA1E9B7126399E46

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20200511/cc249cf3/signature.sig>

Thank you,

Hope it's the same issue.? Should I add to bug report?

On 11/05/2020 09:56, Ralph Boehme via samba wrote:
> Am 5/11/20 um 8:45 AM schrieb Denis via samba:
>> Hi
>> After Fedora 31 upgrade to F32, samba started to break after more
>> clients connect (up to 10).
>> No config change, no clients change, no sharing changes.? F31 had smb
>> 4.11.7 and was working fine
>> after restarting service it works for a while then it breaks with
>> various messages for each client
> this is probably
>
> https://bugzilla.samba.org/show_bug.cgi?id=14375
>
> which I just created for an issue I tracked down on this weekend.
>
> A fix will ship with the next release.
>
> -slow
>
>
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.