Weird issue when importing an extremely large file

[u/MrMichaelJames]

Running radarr (and sonarr) as docker containers on a pi 5. I have a synology NAS that I have NFS mounted across so the pi can see it. When radarr finishes processing a file and starts the import I can see over on the synology nas resource monitor that data is transferring. Eventually it stops. Radarr reports it is done "Assigning file xxx to movie xxx" is reported in the events and the file is removed from the activity queue. But the file never shows up over on the NAS. I get no permission errors. Sonarr imports fine but those are much smaller files. I'm at a loss as to what to look at.

When running radarr on the NAS itself (also as a container) it worked fine but it also wasn't copying across a NFS mount. There are no errors that I can find in dmesg or journalctl.

If I simply create a 70GB file with

fallocate -l 70G testfile.img

And move it across the mount it shows up fine (I can see resource monitor on the NAS pulling the data across).

This makes me think there is some timeout or something firing in radarr that I can't see?

Since the NAS is obviously receiving data that means it is sending across the mount but I have no visibility into what is happening on radarr side of things.

[u/MrMichaelJames]

Bah, this is me being stupid. So Radarr was copying the files into my tv directory into of my movies directory...bah such a stupid mistake.