main share using pool that it's not supposed to use at all

[thedoginthewok]

I'm having a hard time, trying to explain this.

 

I have a usenet downloader in a docker container that downloads to a ssd pool called SATA_SSD.

When finished, it's supposed to move to the main array.

 

The pool SATA_SSD is also a share called sata_ssd.

The main array is a share called main.

 

The docker container for the usenet client has a container path /media mapped to /mnt/user/

When a download starts, it's supposed to go to /media/SATA_SSD/UsenetDownload/incomplete (mapped to /mnt/user/SATA_SSD/UsenetDownload/incomplete). After finishing the download, it's supposed to go to /media/main/UsenetDownloads/complete (mapped to /mnt/user/main/UsenetDownloads/complete).

 

But what actually happens, is this: the finished download goes on the sata_ssd pool in a directory called main.
It's not visible in /mnt/user/SATA_SSD, but it appears in /mnt/sata_ssd/

 

I have not configured the SATA_SSD share to use the array or the main share to use SATA_SSD, so I have no idea why this is happening.

 

gustav-diagnostics-20240307-0122.zip

[itimpi]

Sounds like your setup is triggering the behaviour described in the Caution in this section 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.