Closed japandler closed 1 year ago
Given that you flipped the path in the Saltbox config and it fixed your issue, it sounds like what you are requesting already exists?
This looks more like a problem with your edits than a mergerfs issue. Be more specific about how your setup is constructed here.
Either way you can just edit the downloads to /mnt/local/downloads/... and then remote path on the arrs.
I have a suggestion to the devs, add "--read-only" on rclone mount remote cloud, that way you didn't have to change documentation, and this problem will not appear any more. upload by cloudplow will still work.
No one tells you to use the remote path, that is handled by mergerfs. Not to mention read only breaks renames. Closing this.
No one tells you to use the remote path, that is handled by mergerfs. Not to mention read only breaks renames. Closing this.
really? in saltbox docs for setting up qbittorrent here https://docs.saltbox.dev/apps/qbittorrent/?h=qbittor#3-setup it uses unionfs folder.
Save files to location: /mnt/unionfs/downloads/torrents/qbittorrent/completed/
Keep incomplete torrents in: /mnt/unionfs/downloads/torrents/qbittorrent/incoming/
Copy .torrent files to: /mnt/unionfs/downloads/torrents/qbittorrent/torrents/
Copy .torrent files for finished downloads to: /mnt/unionfs/downloads/torrents/qbittorrent/torrents/
Additionally you can set monitored folder to: /mnt/unionfs/downloads/torrents/qbittorrent/watched/
Do you realize that unionfs is mergerfs and not remote?
dude, please read initial bug reported, download goes to unionfs, and it somehow write directly to remote, not local. In my case I change rclone_vfs adding --read-only.
There are plenty of other ways it can happen, like you restarting the mergerfs service without restarting the containers because you, or him, don't know how it works. But I'm locking this as it doesn't need solving. The read only "fix" is idiotic as it breaks functionality.
There are plenty of other ways it can happen, like you restarting the mergerfs service without restarting the containers because you, or him, don't know how it works. But I'm locking this as it doesn't need solving. The read only "fix" is idiotic as it breaks functionality.
well, I do a clean install, and not touching anything, and yet it I still getting this error.. or maybe you should change the docs to point "/mnt/local/" instead?
Support is for discord. Regardless mergerfs doesn't allow writes to remote anyway. If you want to suggest changes maybe try understanding how it works first? Remote is set to no create, which doesn't allow writes.
Describe the bug Having downloads write to unionfs merge can generate some interesting errors, depending on setup with multiple HDDs, etc. It's better to have the downloads write to local disks, run whatever post-processing, and then have it merged up.
To Reproduce Steps to reproduce the behavior:
Expected behavior You should expect to see the download go through smoothly.
Screenshots Didn't grab any before figuring out the problem.
Logs
If issue occurs during Ansible playbook, run playbook with
-vv
to output detailed debug log.System Information
Additional context I was able to resolve this issue by changing the config paths from /mnt/unionfs to /mnt/local. Asking for us to have a portion of documentation that either calls this out, or a setting that allows us to change it specifically for our torrents and NZBs.