I may have written this a bit unclear, the client is a windows machine. Using Ubuntu as a client works perfectly.
One scenario that reproduces the problem:
______
Server:
Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) with Samba 4.11.6-Ubuntu
Client:
Windows 10 (10.0.18363)
Mounted a share from the server with the native windows smb client. The server displays this connection with the following parameters (smbstatus): Protocol SMB3_11, no encryption, signing partial(AES-128-CMAC)
Action:
Running git clone on the client in a shared directory
Result:
git console out: fatal: cannot create directory at 'images': Directory not empty
git fails.
Switching servers:
______
When i switch the Server to a Ubuntu 18.04 with Samba 4.7.6 or a CentOS with Samba 4.11 and leave the client configuration as-is, the git clone action on the client does NOT fail.
I also tried setting the smb server log level to debug, but it does not log anything when the error on the client occurs.
Below here is my smb.conf:
___________________________________________________________________________
#======================= Global Settings =======================
I may have written this a bit unclear, the client is a windows machine. Using Ubuntu as a client works perfectly.
One scenario that reproduces the problem:
______
Server:
Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) with Samba 4.11.6-Ubuntu
Client: AES-128- CMAC)
Windows 10 (10.0.18363)
Mounted a share from the server with the native windows smb client. The server displays this connection with the following parameters (smbstatus): Protocol SMB3_11, no encryption, signing partial(
Action:
Running git clone on the client in a shared directory
Result:
git console out: fatal: cannot create directory at 'images': Directory not empty
git fails.
Switching servers:
______
When i switch the Server to a Ubuntu 18.04 with Samba 4.7.6 or a CentOS with Samba 4.11 and leave the client configuration as-is, the git clone action on the client does NOT fail.
I also tried setting the smb server log level to debug, but it does not log anything when the error on the client occurs.
Below here is my smb.conf: _______ _______ _______ _______ _______ _______ _______ _______ _______ _____
_______
#====== ======= ======= === Global Settings ======= ======= ======= ==
[global]
## Browsing/ Identification ###
workgroup = WORKGROUP
server string = nas
dns proxy = no
#### Debugging/ Accounting ####
log file = /var/log/ samba/log. %m
max log size = 50
syslog = 0
panic action = /usr/share/ samba/panic- action %d
guest ok = no
load printers = no
####### Authentication #######
server role = standalone server
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u snew\s* \spassword: * %n\n *Retype\ snew\s* \spassword: * %n\n *password\ supdated\ ssuccessfully* .
passwd chat = *Enter\
pam password change = yes
map to guest = never
security = user
############ Misc ############
usershare allow guests = no
[data] keeptree = Yes
comment = "Data Storage"
path = /media/data
writeable = yes
browseable = yes
read only = no
guest ok = no
valid users = @shareadmins
vfs objects = recycle
recycle:
force create mode = 0770
force directory mode = 0770