I guess using LVM on an old raspberry pi 3B+ was not the smartest idea :/ ! As expected the pi 3b+ can handle qbittorrent and piHole without to much load average…

After switching from LVM+EXT4 to a single EXT4 partition, I can download, check file integrity and resolve DNS at the same time without my dns resolution hanging !

Solution:

• Install piHoleOS on a simpler filesystem without LVM (ext4)
• Take qbittorrent out of docker and install it barebone on the device (qbittorrent-nox)

---

Hello :))

I’m relatively new to the pi and all the ecosystem (ARM, SBC…) and I’m kinda intrigued on what’s happening here if someone has some info to share.

I generally work on debian for my server stuff but found an old never used RPi 3B+ in one of my boxes. Installed RPi OS lite based on debian bookworm and docker with the pihole container as DNS server for my home network.

Works great and does hold all my DNS requests without issues. However, yesterday I migrated my qbittorrent stuff (mostly linux ISO 😅) on the RPi, on an external HDD over USB.

While uploading works fine without issues for +/- 100 torrent files, when downloading OR checking the files integrity the RPi is chocking really hard making the DNS request slowdown and even unresponsive…

I did some search and from my findings the USB is a hard bottleneck for file transfer on the pi 3b+ and qbittorrent in a container adds alot of overheat too, so I checked and moved everything out of the container and installed qbittorrent-nox which does improve the situation but it still makes the DNS request on pihole impossible when downloading or checking file integrity.

---

I this some kind of bug, known issue? RPi is cool stuff but If it can’t hold or stand a medium hungry service, that’s kinda a bummer… It’s not doing that much of work, It’s just resolving DNS and downloading a file over the torrent protocol.

Somone similar issue, observation, insight or solution? Or is the pi not meant to hold a torrenting service?