Linked folders are not visible to rutorrent

Ariloum commented 6 months ago

Support guidelines

[X] I've read the support guidelines

I've found a bug and checked that ...

[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem

Description

I have created linked folder so it pops up in the "completed" default rutorrent folder: ln -s /mnt/user/testfolder /mnt/user/torrents/complete

I changed user to nobody: chown -h nobody:users testfolder

lrwxrwxrwx 1 nobody users 18 May 27 23:20 testfolder -> /mnt/user/testfolder

But rutorrent didn't show it in it's directory tree if I try to change some torrrent folder by clicking "Save to..." on it's popup menu.

Expected behaviour

Linked folders working as usual fodlers

Actual behaviour

Linked folders didn't shows

Steps to reproduce

ln -s /mnt/user/testfolder /mnt/user/torrents/complete chown -h nobody:users testfolder

Docker info

Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 6
  Running: 2
  Paused: 0
  Stopped: 4
 Images: 6
 Server Version: 20.10.21
 Storage Driver: btrfs
  Build Version: Btrfs v5.10.1 
  Library Version: 102
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 1c90a442489720eec95342e1789ee8a5e1b9536f
 runc version: v1.1.4-0-g5fd4c4d1
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.19.17-Unraid
 Operating System: Slackware 15.0 x86_64 (post 15.0 -current)
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 15.04GiB
 Name: Tower
 ID: X6AX:P2PS:RCYZ:4BU5:7UGH:CXSH:PWMP:EBCR:UDU2:4SNH:H65S:4VVL
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

Docker Compose config

docker: 'compose' is not a docker command.

Logs

<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><struct>
<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><struct>
<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><struct>
<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><struct>
<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><struct>
<member><name>faultCode</name>
<value><i4>-501</i4></value></member>
<member><name>faultString</name>
<value><string>Could not find info-hash.</string></value></member>
</struct></value>
<value><array><data>
<value><i4>0</i4></value>
</data></array></value>
<value><array><data>
<value><i4>0</i4></value>
</data></array></value>
<value><array><data>
<value><i4>0</i4></value>
</data></array></value>
<value><array><data>
<value><i4>0</i4></value>
</data></array></value>
</data></array></value></param>
</params>
</methodResponse>

Additional info

No response

stickz commented 6 months ago

It's required to change $topDirectory if you would like to increase visibility. https://github.com/Novik/ruTorrent/blob/201ef857f1863df6b5463c31fa27434915116717/conf/config.php#L36

Also, you may experience problems with the BTRFS on rTorrent. It does not like COW file systems. It's recommended to use EXT4.

Ariloum commented 6 months ago

Also, you may experience problems with the BTRFS on rTorrent. It does not like COW file systems. It's recommended to use EXT4.

I'm using default filesystem on the Unraid - it's XFS

I didn't get what you mean about root directory, I'm using default directories with docker rutorrent-crazymax, it has "completed" folder and move finished torrents here from the "temp" folder (it also makes subfolders in completed folder by torrent label name), all I did is just making linked folder inside that "complete" folder, so I think it should be visible for rutorrent if not filtered specially for unknown reason?

so for rutorrent my directory structure looks like this: /completed /completed/games /completed/books /completed/testfolder <- this one is link I made to another folder outside of rutorrent share ... /temp /temp/downloading-folder-1 /temp/downloading-folder-2 /temp/downloading-torrent-1 /temp/downloading-torrent-2 ...

crazy-max / docker-rtorrent-rutorrent