Dear fellow Linux Users,

I have a very strange problem which I cannot really pin down.

I use Debian12 System which mounts a cifs share via pam mount. On logon of a user these directories are mounted correctly. All files are visible and contain the correct information.

New files can be created and deleted on the network share - these are also visible on other system which use the network share.

However when I try to copy a file by
cp /mnt/user/USERNAME/test1 /mnt/user/USERNAME/test2
it either takes forever and freezes the terminal or it instantly tells me "killed".

The network share is running since 10 years and is working fine on other machines, even debian12 ones.

The affected computer mounts 5 network shares, all with different options, all of the network shares have the issue that cp can not be used and is killed immediately.
On other computers (with older OS) I setup all the network shares are running fine with identical mount options.

Do you have any idea where to search for an error? I double checked all permissions. All folders are read/write/executable by the group.

Greetings
Jim

If the mounted name is used, does the issue still come out?

Thank you for your reply. What do you mean by "mounted name"? Do you mean if I do not mount anything and use the mount point directory locally?

(I can write/copy/delete files on my local home partition on the affected computer)

The problem still persits, even a complete reinstall leads to the same problem. I am quite baffled by this, help would be much appreciated.

There seems to be a samba bug, maybe this is the reason?
https://forum.manjaro.org/t/cant-cop...-update/155049

Your original post seems to say that this works on other computers running Debian 12.

So what's different? Either a hardware problem or a network problem.

Have you tried mounting the relevant shares a different way, such as sshfs?

I found the solution. The newest Linux kernel has a bug leading to this.
https://forum.manjaro.org/t/cant-cop...-update/155049

To fix it you need to go to an even newer kernel, here is a great tutorial:
https://www.linuxcapable.com/how-to-...-debian-linux/

It is now working!!!

The big difference was that the affected share were mounted via samba. The bug affects only samba shares.