Krusader not moving files away from unprotected disk to array, while Windows does

[TallMan206]

Hi all,

 

I am running UnRAID 6.12.4 with binhex-krusader.

My array layout: 

Array with 3x 8TB and 2x 10TB parity

Cache pool with 2x NVME 500G with my Docker and VM data

1 SSD 1TB for downloads and processing those downloads. The resulting data should move to the Array.

 

My shares: 

Data: Cache to Array

Media: Array 

Downloads: Download SSD only

Backups: Array

 

The problem: when I have downloaded something and I want to move the unpacked files to my Media share (Array only) and I do this via Krusader, the data stays on the Downloads drive, just in a folder called like the folder where I want to actually have it on the Array.

When I move via Windows, the files are indeed dissapearing from the Downloads drive to the Array as intended. 

 

I do move the files in Krusader within the Shares /mnt/user/Downloads to /mnt/user/Media so I would expect the files to dissapear from the Downloads drive to the Media drive however, this is not the case when using Krusader. 

 

What can I do to make sure my files are moved correctly? The Downloads drive is an unprotected drive so NO files should stay there after I moved them to the array. It's just for downloading and processing those files.

 

Screenshots 'Downloads' is the Download drive as it should be (only with the Download folder).

'Moving' is where you can see that I am moving withing the Shares, not on disk level.

'Moved' is where you see the folder Media/Muziek on my Downloads drive, where it should NOT be, and also the Mover does NOT move it to the Array. 

 

Does someone know how to make Krusader work correctly?

 

Thanks.

 

 

[Squid]

Without seeing the docker run command, what you're seeing is probably to be expected (and will happen on any OS -> not just Krusader / Unraid)

 

Presumably, you've mapped something like /mnt or /mnt/user to /Unraid Shares

 

What every OS in the world attempts to do is that when you're accessing everything from a single mount point, it will do a rename instead of a copy / delete to move the file.  Because the rename succeeds, effectively the file is still on the same drive.

 

Windows works in this case because you're accessing each share from a different mount point (each share that appears within windows is a different mount).  Because the source and destination are different mount points Windows has to do a copy / delete since a rename will automatically fail.

 

Probably the best thing to do here is either continue to use Windows for this type of operation or try Dynamix File Manager instead, or set up the shares so that they will move to the array, or work with /mnt/diskX exclusively within Krusader (do not mix copying / moving with /mnt/diskX and /mnt/user )

 

 

 

[TallMan206]

That made total sense! Thanks for this 'trigger'! It indeed works, but I just did not see it haha.

 

What I did, I mapped to the shares (and not to /mnt/user anymore and moving works now like intended!

 

Thanks again!