Hardlink failed due to I/O error - Cross-link device

[Paul68kdmd]

Hello,

I get an error message described in the title when I run jlesage/docker-filebot https://github.com/jlesage/docker-fileb ... me-ov-filefor hardlinks.







It seems to be fine when I run it through a TEST




Both the '/watch' and '/output' folders are with in the same file system. Strangely, FB makes all the folders (exactly as I wanted them), but does not make hardlinks.

Sorry, I understand this is a fork of your work. Is there anything you can guide me to?

[rednoah]

Both the '/watch' and '/output' folders are with in the same file system. Strangely, FB makes all the folders (exactly as I wanted them), but does not make hardlinks.

/watch and /output are 2 separate mount points right there, thus definitely not on the same file system from the container point-of-view.


Please read Notes on --action MOVE and --action HARDLINK for details.


You'll want to make all your input / output folders accessible via a single mount point / single file system from the container-point-of-view, and then process files within that mount point:

yml: Select all

volumes:
  - /volume2/data:/storage

[Paul68kdmd]

I was able to get it to work like this.

Thank you, so much, Red!