SMB shares mounted via cifs client can not re open files saved by the client

English Network/Internet
1

Hey there I have two Tumbleweed machines one is my main machine while the 2nd one is a back up rig and an inhouse server for serveral things.

I have setup an SMB server which worked very well over a very long time and I have mounted all SMB shares locally on my main rig via cifs:

//z003/data/ /z003/data cifs nofail,rw,uid=1000,gid=users,serverino,dir_mode=0770,file_mode=0770,credentials=/root/.smb/cred 0 0

//z003/data2/ /z003/data2 cifs nofail,rw,uid=1000,gid=users,serverino,dir_mode=0770,file_mode=0770,credentials=/root/.smb/cred 0 0

My server has samba: Samba version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 installed

SMB status:


Samba version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              
----------------------------------------------------------------------------------------------------------------------------------------
4607    vortex       users        192.168.178.25 (ipv4:192.168.178.25:58572) SMB3_11           -                    partial(AES-128-CMAC)

Service      pid     Machine       Connected at                     Encryption   Signing     
---------------------------------------------------------------------------------------------
IPC$         4607    192.168.178.25 Sa Nov  2 14:52:53 2019 CET      -            -           
Data2        4607    192.168.178.25 Sa Nov  2 14:52:53 2019 CET      -            -           
Data         4607    192.168.178.25 Sa Nov  2 14:52:53 2019 CET      -            -           

No locked files

The situation:

  • If I create a file from the client machine (which has the smb shares mounted via cifs) I can not open the file for editing (independent of application)
  • If I create a file on the server I can open it, change it, save it, close it AND re open it on my client and on the server.

So files created by the client are not able to be opened by the client BUT I can delete them but not copy them.

I checked /var/log/messages and /var/log/samba/smb.log and /var/samba/nmb.log and found nothing related to the file situation they are silent on any file creation

smb.conf:


# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
    workgroup = ZRAY
    passdb backend = tdbsam
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    include = /etc/samba/dhcp.conf
    logon path = \\%L\profiles\.msprofile
    logon home = \\%L\%U\.9xprofile
    logon drive = P:
    usershare allow guests = No
    wins support = Yes

## Share disabled by YaST
# [homes]
#    comment = Home Directories
#    valid users = %S, %D%w%S
#    browseable = No
#    read only = No
#    inherit acls = Yes

## Share disabled by YaST
# [profiles]
#    comment = Network Profiles Service
#    path = %H
#    read only = No
#    store dos attributes = Yes
#    create mask = 0600
#    directory mask = 0700

## Share disabled by YaST
# [users]
#    comment = All users
#    path = /home
#    read only = No
#    inherit acls = Yes
#    veto files = /aquota.user/groups/shares/

## Share disabled by YaST
# [groups]
#    comment = All groups
#    path = /home/groups
#    read only = No
#    inherit acls = Yes

## Share disabled by YaST
# [printers]
#    comment = All Printers
#    path = /var/tmp
#    printable = Yes
#    create mask = 0600
#    browseable = No

## Share disabled by YaST
# [print$]
#    comment = Printer Drivers
#    path = /var/lib/samba/drivers
#    write list = @ntadmin root
#    force group = ntadmin
#    create mask = 0664
#    directory mask = 0775

[Data]
    inherit acls = Yes
    path = /data
    read only = No
    directory mask = 0770
    create mask = 0770

[Data2]
    inherit acls = Yes
    path = /home/vortex/.smb
    read only = No
    directory mask = 0770
    create mask = 0770

Do someone know whats going on here out of nowhere (Just ran a couple of Tumbleweed updates but they did not cause any issues in the past until now)

Thanks in advance :slight_smile:

2

Installed all latest updates and issue still persists.
Can someone please help, this is a really urgend matter because I have a lot of project files on my server machiene and I am not able to work on anything.

The issue in short:

  • Client has SMB shares mounted via cifs
  • Client can access all files on the smb shares
  • Client can open files and change and save files on the smb share
  • But if the client CREATES a new file it is broken for the client
    – The client can not open, modify, copy or move that file
    – For the server everything is still okay (if logged into the server via SSH or the desktop session)
    — Server can open, move, copy, edit and save the files which are broken for the client.
    I double checked the SMD user setup, and also all file permissions are ok.

So the client side I am unable to open a file created in the past week every file created by the client before that time are still okay.

A short video to better visualize the issue: https://youtu.be/9ftVatI31Z8
While doing the screen cast I noteced file permission mismatch on the client and server side at files created by the client:

File permissions at client side: -rwxrwx—
File permissions at server side: -rwxrw----

3

Can you show us the full ownership details?

4

On the client side:


-rwxrwx--- 1 vortex users 0  5. Nov 18:23 file-by-client.txt
-rwxrwx--- 1 vortex users 0  5. Nov 18:23 file-by-server.txt

On the Server side:


-rwxrw---- 1 vortex users   0  5. Nov 18:23 file-by-client.txt
-rw-r--r-- 1 vortex users   0  5. Nov 18:23 file-by-server.txt

The SMB User is also named vortex if this makes any difference.
Thank you in advance :slight_smile:

5

Nothing interesting reported in the samba server logs?

6

All the logs on the server side seem to be quite normal

log.smbd:


Z003:/var/log/samba # tail -fn 50 log.smbd
[2019/11/02 09:09:13.124997,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 09:09:13.453064,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/02 13:01:19.761184,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 13:01:19.778159,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/02 13:01:54.244113,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 13:01:54.258943,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/02 13:11:40.375090,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 13:11:40.394278,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/02 13:59:08.185980,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 13:59:08.308909,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/02 14:52:14.058812,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/02 14:52:14.074346,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/03 10:00:11.020397,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/03 10:00:11.367726,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/04 16:56:25.774378,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/04 16:56:25.878127,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/04 21:34:45.987920,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/04 21:34:46.146285,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2019/11/05 18:11:12.080501,  0] ../../source3/smbd/server.c:1775(main)
  smbd version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2019
[2019/11/05 18:11:12.192991,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
  daemon_ready: daemon 'smbd' finished starting up and ready to serve connections

log.nmbd:


Z003:/var/log/samba # tail -fn 50 log.nmbd
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:08:15.148918,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:13:21.822965,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:18:12.106769,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:23:15.371455,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:28:21.822188,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:33:35.339784,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:38:41.649660,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:43:31.945248,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:48:35.589678,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:53:45.909479,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 21:58:39.524293,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 22:03:47.337282,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 22:09:05.506251,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 22:14:07.518326,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 22:18:57.826598,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
[2019/11/05 22:24:05.768414,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
  This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.

messages:


tail -fn 100 messages | grep "nmbd"
2019-11-05T22:14:07.519222+01:00 Z003 nmbd[1690]: [2019/11/05 22:14:07.518326,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
2019-11-05T22:14:07.532124+01:00 Z003 nmbd[1690]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
2019-11-05T22:14:07.546710+01:00 Z003 nmbd[1690]:   This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
2019-11-05T22:18:57.827318+01:00 Z003 nmbd[1690]: [2019/11/05 22:18:57.826598,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
2019-11-05T22:18:57.827694+01:00 Z003 nmbd[1690]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
2019-11-05T22:18:57.827793+01:00 Z003 nmbd[1690]:   This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
2019-11-05T22:24:05.769094+01:00 Z003 nmbd[1690]: [2019/11/05 22:24:05.768414,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
2019-11-05T22:24:05.785065+01:00 Z003 nmbd[1690]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.26 for name ZRAY<1d>.
2019-11-05T22:24:05.785966+01:00 Z003 nmbd[1690]:   This response was from IP 192.168.178.33, reporting an IP address of 192.168.178.33.
7

It’s not clear to me what might be going on here. Are you in a position to test behaviour via a Windows or openSUSE Leap 15.1 samba client perhaps?

8

The weird thing is if I connect to the SMB shares over the SMB protocol I can access those files and also copying them. But opening files via smb://root/to/file for example will automatically copy them into kio’s temp directory and that’s why I used to mount them via cifs so the files stay where they are and I don’t forget to copy changed files back to the shares. Also some project files will miss external data since they are no longer at the same relative path when opening the file from the kio temp directory.

So I assume there might be an issue with cifs?

To test this behaviour I might need to set up another Linux box which mounts the shares via cifs I think?
And also I am not sure if testing Windows will help here or dose Windows also have a cifs like method to mount shares? Afaik Windows will handle the shares like a “normal” smb connection would do?

I’ll try to set up a Leap installation in a virtual box and see if it is working.

9

Yes, specifically to compare behaviour when using an older samba client versiom.

I’ll try to set up a Leap installation in a virtual box and see if it is working.

Great let us know how you get on.

10

So I set up a Leap 15.1 machine in a virtual box (Gnome-Boxes) and facing the exact same issue at default configuration. I only ran updates on the virtual machine.
The Leap 15.1 machine is as much default as possible /except of the updates).

fstab of virtual machine:


//z003/data/                               /z003/data              cifs   nofail,rw,uid=1000,gid=users,serverino,dir_mode=0770,file_mode=0770,credentials=/home/virttex/.smb/cred 0 0
//z003/data2/                              /z003/data2             cifs   nofail,rw,uid=1000,gid=users,serverino,dir_mode=0770,file_mode=0770,credentials=/home/virttex/.smb/cred 0 0

But the smb status shows something new all files created by the Leap machine are now listed as locked files even if none of these files are opened any where.


vortex@Z003:~> sudo smbstatus 

Samba version 4.11.0-git.95.c88b5f2c0c6SUSE-oS15.5-x86_64
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              
----------------------------------------------------------------------------------------------------------------------------------------
15775   vortex       users        192.168.178.25 (ipv4:192.168.178.25:53266) SMB3_11           -                    partial(AES-128-CMAC)
24331   vortex       users        192.168.178.25 (ipv4:192.168.178.25:57904) SMB3_11           -                    partial(AES-128-CMAC)

Service      pid     Machine       Connected at                     Encryption   Signing     
---------------------------------------------------------------------------------------------
Data2        24331   192.168.178.25 Mi Nov  6 23:29:53 2019 CET      -            -           
Data         24331   192.168.178.25 Mi Nov  6 23:29:53 2019 CET      -            -           
IPC$         15775   192.168.178.25 Mi Nov  6 22:50:14 2019 CET      -            -           
Data2        15775   192.168.178.25 Mi Nov  6 22:50:14 2019 CET      -            -           
Data         15775   192.168.178.25 Mi Nov  6 22:50:14 2019 CET      -            -           
IPC$         24331   192.168.178.25 Mi Nov  6 23:29:53 2019 CET      -            -           

Locked files:
Pid          User(ID)   DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap.txt   Wed Nov  6 23:30:27 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap.txt   Wed Nov  6 23:30:27 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:50 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:51 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:52 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:52 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
24331        1000       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /home/vortex/.smb   file-by-leap-2.txt   Wed Nov  6 23:30:53 2019
15775        1000       DENY_NONE  0x80        RDONLY     NONE             /home/vortex/.smb   .   Wed Nov  6 23:08:56 2019
15775        1000       DENY_NONE  0x80        RDONLY     NONE             /data   .   Wed Nov  6 22:56:24 2019
15775        1000       DENY_NONE  0x80        RDONLY     NONE             /data   .   Wed Nov  6 22:56:26 2019
15775        1000       DENY_NONE  0x80        RDONLY     NONE             /data   .   Wed Nov  6 22:56:27 2019

Don’t get confused by the dublicate ips and doubled used data directory because the virual Leap 15.1 installation is on my main machine and seems to share the same IP Address.

neofetch of the Leap machine:


           .;ldkO0000Okdl;.              virttex@localhost 
       .;d00xl:^''''''^:ok00d;.          ----------------- 
     .d00l'                'o00d.        OS: openSUSE Leap 15.1 x86_64 
   .d0Kd'  Okxol:;,.          :O0d.      Host: KVM/QEMU (Standard PC (Q35 + ICH9, 2009) pc-q35-4.1) 
  .OKKKK0kOKKKKKKKKKKOxo:,      lKO.     Kernel: 4.12.14-lp151.28.25-default 
 ,0KKKKKKKKKKKKKKKK0P^,,,^dx:    ;00,    Uptime: 17 mins 
.OKKKKKKKKKKKKKKKKk'.oOPPb.'0k.   cKO.   Packages: 2214 (rpm) 
:KKKKKKKKKKKKKKKKK: kKx..dd lKd   'OK:   Shell: bash 4.4.23 
dKKKKKKKKKKKOx0KKKd ^0KKKO' kKKc   dKd   Resolution: 1920x1005 
dKKKKKKKKKKKK;.;oOKx,..^..;kKKK0.  dKd   DE: KDE 
:KKKKKKKKKKKK0o;...^cdxxOK0O/^^'  .0K:   WM: KWin 
 kKKKKKKKKKKKKKKK0x;,,......,;od  lKk    Theme: Breeze [KDE], Breeze [GTK2/3] 
 '0KKKKKKKKKKKKKKKKKKKKK00KKOo^  c00'    Icons: breeze [KDE], breeze [GTK2/3] 
  'kKKKOxddxkOO00000Okxoc;''   .dKk'     Terminal: konsole 
    l0Ko.                    .c00l'      CPU: AMD Ryzen 7 1800X (16) @ 3.599GHz 
     'l0Kk:.              .;xK0l'        GPU: Red Hat, Inc. Virtio GPU 
        'lkK0xl:;,,,,;:ldO0kl'           Memory: 1179MiB / 5986MiB 
            '^:ldxkkkkxdl:^'
11

Yesterday I had some updates for both TW machines including some samba packages and now everything is working again as expected. Looks like there was an bug with the smb packages. :slight_smile:

Server:


vortex@Z003:~> sudo smbstatus 
[sudo] Passwort für root: 

Samba version 4.11.2-git.99.f93cc798f2eSUSE-oS15.5-x86_64
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              
----------------------------------------------------------------------------------------------------------------------------------------
1966    vortex       users        192.168.178.25 (ipv4:192.168.178.25:34496) SMB3_11           -                    partial(AES-128-CMAC)
1965    vortex       users        192.168.178.25 (ipv4:192.168.178.25:34494) SMB3_11           -                    partial(AES-128-CMAC)

Service      pid     Machine       Connected at                     Encryption   Signing     
---------------------------------------------------------------------------------------------
Data2        1965    192.168.178.25 Sa Nov  9 11:29:05 2019 CET      -            -           
IPC$         1965    192.168.178.25 Sa Nov  9 11:29:05 2019 CET      -            -           
IPC$         1966    192.168.178.25 Sa Nov  9 11:29:05 2019 CET      -            -           
Data         1966    192.168.178.25 Sa Nov  9 11:29:05 2019 CET      -            -           

No locked files

vortex@Z003:~>

and the client runs now:


[vortex@Z004:~]% smbclient -V                                                                                  
Version 4.11.2-git.99.f93cc798f2eSUSE-oS15.5-x86_64

also the virtual test Leap 15.1 machine can now access, edit, open, created files as expected with no updates. So I assume it was something wrong with the smb server packages.

Thank you for all your help :slight_smile: