Hi,
I am new using Hardlink and I would like to know if the Move action could break a Hardlink file and make a copy/delete of it instead of moving the hardlink directly after a Rename
I recently saw in my library that the movie filebot have renamed and moved from my watch folder to my output are not hardlinked anymore
My download client send in /Torrent and then I use Radarr to make hardlink to /watch folder for the AMC to do is job to rename and move to my /output but doing that break the hardlink file and make a copy instead
is it normal or I did something wrong?
Thanks for help
is Move action could break a already hardlink file?
Re: is Move action could break a already hardlink file?
the reason why I am not using filebot to directly duplicate or hardlink is because I a also downloading movie/tv show from another source outside of Radarr
Source1 sent to -> /watch
Torrent download client sent to -> /torrents
Radarr from /torrents sent to -> /watch
Filebot only watching /watch
is it better I use cmd-line from the download client to do duplicate instead of Radarr? -> I am also new using Radarr lol
Source1 sent to -> /watch
Torrent download client sent to -> /torrents
Radarr from /torrents sent to -> /watch
Filebot only watching /watch
is it better I use cmd-line from the download client to do duplicate instead of Radarr? -> I am also new using Radarr lol
Re: is Move action could break a already hardlink file?
No. Hardlinks (i.e. normal files) cannot break, in the "symbolic link" sense. That said, if you move a hardlink (i.e. normal file) from one file system to another, then the OS will physically copy the data to a new file (i.e. new hardlink) on the target file system.
Keep in mind that "normal file" and "hardlink" are the exact same thing:
https://en.wikipedia.org/wiki/Hard_link
You are thinking of symlinks, which are just "text files" that contain the file path to another file, and so symlinks can break if the target file paths no longer exists:
https://en.wikipedia.org/wiki/Symbolic_link
If you are using docker then you need to be aware of file system boundaries from the point-of-view of the container:
https://github.com/filebot/filebot-dock ... n-hardlink
You'll want to use --action hardlink to hardlink or fail to test your setup. If you use --action duplicate then filebot will do hardlink if possible, copy if necessary and so it'll always work one way or another.
Keep in mind that "normal file" and "hardlink" are the exact same thing:https://en.wikipedia.org/wiki/Hard_link
You are thinking of symlinks, which are just "text files" that contain the file path to another file, and so symlinks can break if the target file paths no longer exists:https://en.wikipedia.org/wiki/Symbolic_link
If you are using docker then you need to be aware of file system boundaries from the point-of-view of the container:https://github.com/filebot/filebot-dock ... n-hardlink
You'll want to use --action hardlink to hardlink or fail to test your setup. If you use --action duplicate then filebot will do hardlink if possible, copy if necessary and so it'll always work one way or another.