A problem is that RPiOS Bookworm is not Debian Bookworm. There are many changes/patches in userspace. Look for all packages named/tagged rpt? or rpi?. A sudden un-announced bpo12 had ruined my audio on Pi4 recently. And then it is a vendor kernel, not the standard Debian12 one used worldwide on way more computers. And closed-source proprietary firmware, not UEFI/BIOS. And also a non-PCIE attached GBit ethernet.First of all I have just run some tests that I should have run a few days back. As I have said I tested file transfer from a Pi4 running Bullseye without any problems. As the page file size is 4K I have rerun the tests to ensure I was trying with enough file transfers. Today I have transferred over 120GB without issue.
The telling test was when I moved the Bookworm SD to the Pi 4 (with the 4k page size). Each time I managed to move a single 10GB file but the system hung every time I tried to move a second file.
From this we can conclude there is not, as I had originally supposed a NVME problem, as it also occurs when only a SD card is involved. As the problem can also be seen on a Pi 4 it is not a Pi5 problem. This leaves us with Bookworm and the NAS. Suggesting there is a change in the handling of CIFS data transfers, in Bookworm, which triggers a problem. I must admit my thought is to agree with the possibility of a memory leak but obviously an obscure one. Otherwise it would have been discovered by others.
You might try or have a look at
https://github.com/pftf/RPi4
https://raspi.debian.net/tested-images/
Those allow you to run vanilla Debian12, still on top of proprietary firmware version of course. That firmware version can also matter, RPiOS Bookworm and RPiOS Bullseye have different firmware version. On Pi4, I have used many manual changes/mixes as other Linux Distros have other versioning and release strategy.
Statistics: Posted by redvli — Mon Nov 18, 2024 8:01 am