33
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Jul 2023
33 points (94.6% liked)
Selfhosted
40406 readers
239 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I would look into either a permissions issue (the daemon having no permissions to write in your target folder), or a faulty disk issue. I’ve had a similar issue in the past and the former was the cause.
Your description seems coherent with the torrent downloading normally until the memory buffer is full, and then failing when the data is attempted to be written to the disk.
Thanks. Your last sentence really makes sense. It's writing to a NAS, and sometimes the download speed is clearly higher then the NAS max write speed.