Open Pheromir opened 2 months ago
Have you read the documentation about how to use the pre-allocate feature? I don't see the environment variable in your config.
Yes, had it added earlier, but removed it later on, as the documentation states that 0 is the default behaviour (and looking into the rtlocal config in the container seemed to confirm that).
Added the EnvVar again and tested the download. Can confirm, that it still happens.
I just tested this outside the docker container. Option 2 works properly. Option 0 always behaves as option 1. This is a rTorrent issue.
Thanks for testing! Does it have anything to do with the latest commit you reversed, or do you want me to open a separate issue on your repo?
Please allow further time to test the vanilla rakshasa version of rTorrent. I'm almost sure the issue started there.
If this is the case, the best path forward for a solution is to request a fix there and backport it to rtorrent stickz.
Thanks for testing! Does it have anything to do with the latest commit you reversed,
Nope, I'm working on resolving a separate software crash with torrent rechecking.
Support guidelines
I've found a bug and checked that ...
Description
When starting a download, rtorrent always seems to preallocate the files on the disk, even if option is explicitly set to 0 in config
Expected behaviour
Files shouldn't get preallocated if option not set to 1 or 2
Actual behaviour
Files always get preallocated after they started downloading
Steps to reproduce
Docker info
Docker Compose config
Logs
Additional info
I also made sure that the .rtlocal.rc file within the container says "system.file.allocate.set = 0". Not sure if it's a problem with the image or the rtorrent build, but I don't think that I can test it properly without docker here.
Screenshot of the allocated file on the filesystem, with the incomplete files in rtorrent: