Created attachment 15948 [details]
Log of all errors
I was using a home compiled samba v4.11.8, i made a copy of a directory on the server side (using rsync command) in a samba shared directory.
On a Windows 7 computer, i tried to access to those files, but, without any reasons, all my share became unavailable under this computer (all others machines connected to my shares have ran fine), i've checked logs and i found a PANIC action from samba (check the file attached).
It's seems to me that is a bug, but i really don't know what is it concretely.
Thanks for your understanding !
Comment on attachment 15948 [details]
Log of all errors
On possible reason is that the filesystem where locking.tdb is stored is full. Can you check that?
Currently, locking.tdb is located in /run/lock/samba
With df -H, i've see that :
This is a tmpfs filesystem
The filesystem's size is 5,3M, but there only 173k available space left.
This can be cause the error ?
5.3MB is not very much for locking.tdb, in particular if you're dealing with more than a handful of files. Please put locking.tdb on a file system with a lot more space.
Do you know how to increase the size of this filesystem ?
As I know, the mount point is managed by systemd. And the mount point isn't specified in fstab
(In reply to ikdc.services from comment #4)
> Do you know how to increase the size of this filesystem ?
> As I know, the mount point is managed by systemd. And the mount point isn't
> specified in fstab
No clue, sorry. This is at least distro-specific. As you compiled Samba on your own, probably you can compile it in a way that Samba puts its locking.tdb somewhere else. You might also try setting "lock directory = /some/dir" in the [global] section of your smb.conf to a file system with more space.
closing as this is not a bug. Please consider https://www.samba.org/samba/support/ or use precompiled samba packages.