Hello,

I have my media in one share (data), structured as follow :

Data/
├── Downloads/
│   ├── DL1.file
│   ├── DL2.file
│   └── ...
└── Media/
    ├── Movies/
    │   ├── Movie 1/
    │   │   └── Movie1.file
    │   └── ...
    └── TV/
        └── Show 1/
            └── Season 1/
                ├── Episode 1
                └── ...

Data is on 2 drives, up until now it was set up as Fill-up, but due to the first disk starting to be a bit full I switched it to High-water, with folder split level only the top 3.
This works fine in Data/Media when manually adding a file, however, when a file is downloaded in Data/Downloads, it is put on the second disk (which is normal), but when the download is complete, it is copied to the appropriate Media directory. But when the directory is on the first disk it doesn't change from disk2 to disk1, which results in episodes from a single season being split on two disks.

 

Is it expexted behaviour? Is there a way to prevent this?

 

Thanks in advance!

How are you doing this move?   ( 1-- From server to PC to server    OR    2-- Using some utility/plugin/Docker installed on the server?) 

 

EDIT:   A move to a new location on the same disk can be virtually instantaneous whereas a disk-to-disk move will take much, much longer!

Edited December 18, 20232 yr by Frank1940

The move from Download to Media is made with a docker. It is supposed to hardlink IIRC

4 minutes ago, Calamonstre said:

The move from Download to Media is made with a docker. It is supposed to hardlink IIRC

You might also want to ask this question in the Docker Support forum...  (Left-click on the Icon in the Docker tab and look for Support in the dropdown menu.)

Will do!

Depending on how the container try’s to do the move it is possible you are falling foul of the behavior described in the Caution on this page of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. 

Ohhh I see. I'm no expert on this, but it may be it. I'll transmit the info on the container support page, they will probably know more than I do.
Thanks for the help!

So, for future reference, This is indeed due to the hardlinking. To prevent the mixing on the drives, hardlink must be turned off.

Thank you to itimpi, Frank1940 and the container support!