[docker] Hardlink within the GUI doesnt work

All your suggestions, requests and ideas for future development
Post Reply
FTW
Posts: 39
Joined: 28 Jan 2022, 09:47

[docker] Hardlink within the GUI doesnt work

Post by FTW »

Hi, so I am trying the HardLink feature in the GUI to manually create them but it failed even if they are on the same device and hdd

I got that error code
HARDLINK: /data/output/TV-FR/Survivor Quebec {tvdb-430991}/Season 01/Survivor Quebec - S01E03 - Lundi - la quotidienne - semaine 1 [1080p].mkv -> /data/Torrent/Survivor.Quebec.S01E03.XXX/Survivor.Quebec.S01E03.XXX.mkv: Cross-device link

Code: Select all

FileBot 5.0.1 (r9665)
JNA Native: 6.1.3
MediaInfo: 22.12
Tools: fpcalc/1.5.1 7z/17.04 unrar/6.12
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2023-03-28 (r895)
Groovy: 4.0.9
JRE: OpenJDK Runtime Environment 17.0.6
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 14 Core / 16 GB Max Memory / 50 MB Used Memory
OS: Linux (amd64)
HW: Linux 30e07dab595a 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
CPU/MEM: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz [MemTotal: 67 GB | MemFree: 816 MB | MemAvailable: 40 GB]
STORAGE: btrfs [/] @ 8 GB | cifs [/QcFLiX] @ 4.2 TB | btrfs [/watch] @ 8 GB | btrfs [/output] @ 8 GB | fuse.shfs [/config] @ 1.9 TB | fuse.shfs [/storage] @ 321 GB | fuse.shfs [/data/Torrent] @ 321 GB | fuse.shfs [/data/watch] @ 321 GB | fuse.shfs [/data/output] @ 321 GB
UID/GID: uid=0(root) gid=0(root) groups=0(root),1,2,3,4,6,10,11,20,26,27
DATA: /config
Package: DOCKER
License: FileBot License PX32157634 (Valid-Until: 2071-12-30)
Done ヾ(@⌒ー⌒@)ノ
thanks
User avatar
rednoah
The Source
Posts: 22923
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Hardlink within the GUI doesnt work

Post by rednoah »

Cross-device link means that /source/path and /target/path are not on the same file system:

Code: Select all

fuse.shfs [/data/Torrent] @ 321 GB
fuse.shfs [/data/output] @ 321 GB

:arrow: You need to keep that in mind, when making host files available within a container via volume mounts, that each volume mount is treated as separate file system from within the container. Please read Notes on --action MOVE and --action HARDLINK for details.
:idea: Please read the FAQ and How to Request Help.
Post Reply