I'm trying to get up to speed on FileBot, and running a few different instances to learn the ins and outs. I've got a docker container on a RPi, accessing it via web GUI, the Windows desktop app, and installed the Synology package on my NAS to try and address some of the issues I was bumping into.
My main question is why Filebot and/or Synology are treating Shared Folders (NFS) as different filesystems. I thought they'd be treated as the same.
I set up an NFS share on /NAS/volume1/plexstuff where I hoped to keep the hardlinks to the renamed files and assets from /NAS/volume1/video, which is where my current movie library is stored.
I initially tried to write the hardlinks via my docker instance, but discovered that each mounted folder in docker was treated as a separate filesystem. So I learned that Filesystems don't just mean the same type (EXT4 vs NTFS vs BRTFS), but has to be the same physical filesystem. OK.
Code: Select all
[HARDLINK] from failed due to I/O error Invalid cross-device link]
Installed the Synology package, and this is where I was surprised. I created a "pristine" folder for my test, but still couldn't create hardlinks from /NAS/volume1/video to /NAS/volume1/plexstuff. But can create hardlinks from /NAS/volume1/video/movies/ to /NAS/volume1/video/plexstuff -- within the same shared folder.
Is that the expected behavior? Can anyone share a link to an explanation so I can wrap my head around it?
Thanks!