Cannot copy "vda2.vfat-ptcl-img.zst" via smb

[Micha]

I cannot copy(/move/delete) the file “vda2.vfat-ptcl-img.zst” (created by Clonezilla) via smb access. I tried it in dolphin, both via kio and then also via mount via fstab, but the error “No permission” always appears. Even with “sudo cp …” I get the error “No permission”. When I copy the file via ssh on the server, it works (of course)! I can then also copy the copy via smb using Dolphin.
All other files created by Clonezilla do not cause any problems, only then “.zst” files!
smb-client:

micha@Klabautermann:/mnt/smb/backup/Efi-img> getfacl vda2.vfat-ptcl-img.zst
# file: vda2.vfat-ptcl-img.zst
# owner: micha
# group: micha
user::rwx
group::r-x
other::r-x

[Micha]

fstab:

//userv.local/backup  /mnt/smb/backup  cifs  credentials=/etc/samba/creds,uid=1000,gid=1000,vers=3.1.1,x-systemd.automount,nofail,_netdev 0  0

[Micha]

After i removed the mount from fstab (and also after a tw update) i cannot write anything in the shared folders with dolphin (kio-mount) anymore. I tried to find a solution with the help of chatgpt, but no luck! I then tried access with Ubuntu and there were no issues. So it is a dolphin/tw issue?

[Micha]

I just discovered that I can create and delete folders with dolphin below the shared folder, and also create subfolders within these folders. I can even create, modify, and delete text files using “Create New” in Dolphin, but copying files to folders does not work! I even cant copy a text-file I newly creatred in a newly created folder!
Chatgpt told me that this is known (and not yet completely fixed) bug in newer KDE/Samba stacks, but all workarounds chatgpt recommended did not work!

[Micha]

It’s getting stranger and stranger. After restarting both the server and the client computer (with tw), I can still create folders in the share from the client, but when I open them in Dolphin, the following message appears: Folder does not exist!
But I can delete this non-existent folder via Dolphin!

[Micha]

testparm -s:

[global]
        log file = /var/log/samba/log.%m
        logging = file
        map to guest = Bad User
        max log size = 1000
        obey pam restrictions = Yes
        pam password change = Yes
        panic action = /usr/share/samba/panic-action %d
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        passwd program = /usr/bin/passwd %u
        server role = standalone server
        server string = %h server (Samba, Ubuntu)
        unix password sync = Yes
        usershare allow guests = Yes
        idmap config * : backend = tdb

[backup]
        comment = backup userv
        create mask = 0666
        directory mask = 0666
        force user = micha
        path = /mnt/backup
        read only = No
        valid users = micha

[kyral]

i have a pretty similar issue, my SMB shares haven’t been changed in months yet a recent system update made dolphin unable to transfer files to the SMB server, i can create new files and directories but copying into the server fails with «Access Denied»

i think the samba/dolphin package is just broken atm

as a workaround, using cp works, use the built in terminal (F4)

[Micha]

My solution is to mount the Samba share in fstab as follows:

//userv.local/backup  /mnt/smb/backup  cifs  credentials=/etc/samba/creds,uid=1000,gid=1000,_netdev,noauto,nofail,x-systemd.automount,x-systemd.after=network-online.target,x-systemd.requires=network-online.target,x-systemd.mount-timeout=2s,x-systemd.idle-timeout=10min  0  0

With “x-systemd.mount-timeout=2s,” it doesn’t take forever for Dolphin to open when the server is unavailable and a share folder was previously open (I have Dolphin set to restore the previous session when it opens)!
Can anyone tell me if it’s generally okay to have a very low timeout, maybe even just 1s?