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

Support for unRAID and docker container users
Post Reply
Paul68kdmd
Posts: 6
Joined: 18 Mar 2024, 12:02

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

Post by 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.

Screenshot

Screenshot

Screenshot

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

Screenshot


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?
User avatar
rednoah
The Source
Posts: 23449
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

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

Post by rednoah »

Paul68kdmd wrote: 22 Mar 2024, 19:55 Screenshot
Paul68kdmd wrote: 22 Mar 2024, 19:55 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.


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


:arrow: 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
:idea: Please read the FAQ and How to Request Help.
Paul68kdmd
Posts: 6
Joined: 18 Mar 2024, 12:02

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

Post by Paul68kdmd »

Screenshot

I was able to get it to work like this.

Thank you, so much, Red!
Post Reply