I think I have encountered a kernel bug and would like help in investigating and (if appropriate) reporting it, as I have no experience in this area.
Since upgrading my Debian 12 workstation PCs to the linux-image-6.1.0-17-amd64 kernel package I am getting an error when I try to copy a file between two locations on mounted samba shares. The copy fails with the message Killed and the destination file is created as a zero bytes file. If I boot the workstations into the previous linux-image-6.1.0-16-amd64 kernel the problem does not occur. Here is a transcript of what happens (directories d1 and d2 are both located on a mounted SAMBA share):An attempt to repeat the copy hangs. ps shows the cp command process is still running, and it cannot be killed, even with kill -9. If I then try to shut down the shutdown hangs for some time with a message something like Job session-2.scope/stop running, and then later in the shutdown it hangs again for a while with messages like systemd-shudown[1]: Waiting for process: 2156 (cp)
The shares are mounted via fstab with a line similar to that below:I have reproduced this with a number of workstations running up-to-date Debian stable and two samba servers - one running a fully up-to-date Debian stable installation, the other a raspberry pi running Raspbian 10 which has not been updated for some time.
I would like to:
Since upgrading my Debian 12 workstation PCs to the linux-image-6.1.0-17-amd64 kernel package I am getting an error when I try to copy a file between two locations on mounted samba shares. The copy fails with the message Killed and the destination file is created as a zero bytes file. If I boot the workstations into the previous linux-image-6.1.0-16-amd64 kernel the problem does not occur. Here is a transcript of what happens (directories d1 and d2 are both located on a mounted SAMBA share):
Code:
$ ls -l d1/total 4-rwxrwx--- 1 andrew andrew 6 Jan 7 22:23 file1.txt*$ ls -l d2/total 0$ cp d1/file1.txt d2Killed$ ls -l d2/total 0-rwxrwx--- 1 andrew andrew 0 Jan 8 07:13 file1.txt*The shares are mounted via fstab with a line similar to that below:
Code:
//SOL/copying /mnt/SOL/copying cifs credentials=/root/.smbcredentials,uid=andrew,gid=andrew,file_mode=0770,dir_mode=0770,x-systemd.automount,x-systemd.mount-timeout=240,x-systemd.idle-timeout=3600 0 0I would like to:
- Determine if this is a real bug or a problem with my setup
- Find out if this is a known bug or something I should report
- Learn how to investigate further if required
- Get some help and advice or how to report this, if necessary
Statistics: Posted by andy638 — 2024-01-08 07:45 — Replies 0 — Views 9