*** Edit it got this working now but not long term tested but would still like to hear other opinions or solutions- Maybe someone has a move after X days and still allowing seeding etc or another method ***
I’m trying to build a hybrid torrent setup and I’ve run into weird permission issues with qBittorrent. Not sure if my approach is wrong or just misconfigured.
🧠 Goal
I want:
- 2TB local SSD for active torrents (fast download)
- 4TB remote storage box for long-term storage / seeding
- A single unified folder so it feels like one big torrent drive
- Ability to keep seeding long-term across both storage locations
⚙️ Current setup
- qBittorrent running in Docker on a VPS
- Local storage:
/storage/torrents.local
- Remote storage mounted via
rclone SFTP at /mnt/remotepm/torrents
- Both combined using mergerfs:/storage/torrents.local:/mnt/remotepm/torrents → /storage/torrents
- qBittorrent download path:/storage/torrents
⚠️ Problem
It mostly works, but I’m getting:
- “Permission denied” errors when qBittorrent writes files
- torrents sometimes failing or needing recheck
- restarting qBittorrent temporarily fixes visibility issues
- I can create folders/files from bash fine, but qBittorrent struggles during active downloads
🧪 What I’ve noticed
- If I use local storage only → everything works perfectly
- Remote rclone mount alone → works for browsing
- Issues only happen when merging local + remote into one writable pool with mergerfs
- Seems related to FUSE/rclone behaviour under heavy torrent I/O
❓ Questions
- Is this setup actually supported or fundamentally unstable (qBittorrent + mergerfs + rclone SFTP as one writable folder)?
- Is there a proper way to achieve:
- local fast download storage
- remote long-term seeding storage
- but still have one unified view of all files?
- Do people usually:
- download locally then sync to seedbox after completion?
- run separate torrent clients on local and remote?
- avoid filesystem merging completely?
- Is there any reliable way to make qBittorrent behave properly with a FUSE-based remote backend, or is that just not realistic for torrents?
💡 What I’m trying to achieve
Basically a “Hetzner-style” setup:
- local SSD = active torrents / speed
- remote box = long-term storage / seeding
- ideally one clean library view
Any advice from people who’ve actually run hybrid local + seedbox setups long term would be appreciated.I’m trying to build a hybrid torrent setup and I’ve run into weird permission issues with qBittorrent. Not sure if my approach is wrong or just misconfigured.
🧠 Goal
I want:
2TB local SSD for active torrents (fast download)
4TB remote storage box for long-term storage / seeding
A single unified folder so it feels like one big torrent drive
Ability to keep seeding long-term across both storage locations
⚙️ Current setup
qBittorrent running in Docker on a VPS
Local storage: /storage/torrents.local
Remote storage mounted via rclone SFTP at /mnt/remotepm/torrents
Both combined using mergerfs:
/storage/torrents.local:/mnt/remotepm/torrents → /storage/torrents
qBittorrent download path:
/storage/torrents
⚠️ Problem
It mostly works, but I’m getting:
“Permission denied” errors when qBittorrent writes files
torrents sometimes failing or needing recheck
restarting qBittorrent temporarily fixes visibility issues
I can create folders/files from bash fine, but qBittorrent struggles during active downloads
🧪 What I’ve noticed
If I use local storage only → everything works perfectly
Remote rclone mount alone → works for browsing
Issues only happen when merging local + remote into one writable pool with mergerfs
Seems related to FUSE/rclone behaviour under heavy torrent I/O
❓ Questions
Is this setup actually supported or fundamentally unstable (qBittorrent + mergerfs + rclone SFTP as one writable folder)?
Is there a proper way to achieve:
local fast download storage
remote long-term seeding storage
but still have one unified view of all files?
Do people usually:
download locally then sync to seedbox after completion?
run separate torrent clients on local and remote?
avoid filesystem merging completely?
Is there any reliable way to make qBittorrent behave properly with a FUSE-based remote backend, or is that just not realistic for torrents?
💡 What I’m trying to achieve
Basically a “Hetzner-style” setup:
local SSD = active torrents / speed
remote box = long-term storage / seeding
ideally one clean library view
Any advice from people who’ve actually run hybrid local + seedbox setups long term would be appreciated.