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?
Hardlink failed due to I/O error - Cross-link device
-
- Posts: 6
- Joined: 18 Mar 2024, 12:02
Re: Hardlink failed due to I/O error - Cross-link device
/watch and /output are 2 separate mount points right there, thus definitely not on the same file system from the container point-of-view.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.
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
Please read the FAQ and How to Request Help.
-
- Posts: 6
- Joined: 18 Mar 2024, 12:02