[I think I found a bug in the mover]

16 hours ago, trurl said:

The user proposes to redesign mover so it always moves from all pools, but I think some users would find that surprising behavior also and some may rely on the existing behavior to insure mover ignores certain files they have put intentionally on other pools (the orphans mentioned in that FAQ I linked above).

 

@jonp

 

I do not concur. I moved the files to a share that is set to "Use cache pool (for new files/directories): YES". This lets me expect two things.

 

1. Some files maybe unprotected, because they are put on a cache first.

2. Once the mover is invoked all files are moved to the array.

 

Files not being moved to the array is the unexpected behavior for that share.

 

I think an additional option might be useful in the share settings: "Have mover check all Cache disk/pools and move onto the array: YES/NO"

 

At the very least clear up the help text. "Mover only moves from the specified Cache disk/pool others are ignored" or something.

[I think I found a bug in the mover]

1 hour ago, jonp said:

Hi there,

 

Please attach a copy of your system diagnostics.  We need to see what's going on exactly here.

unraid-diagnostics-20210915-1611.zip

 

Here you go!

[I think I found a bug in the mover]

1 minute ago, trurl said:

The behavior you are asking about is basically the "orphans" that some people use to keep some of a user share on pool for performance reasons instead of moving to the array. With multiple pools it is perhaps less justified than it was. The FAQ below was written before there were multiple pools, but the principle is the same.

 

I respectfully disagree that I created orphans as I moved files between shares and because the mover worked as soon as I changed the pool.

 

1 minute ago, trurl said:

Since it is by design, maybe make a Feature Request to have it changed. The developers are unlikely to notice it here among the hundreds of threads that get posted every week.

 

I will thank you! Do you know where I can do that?

[I think I found a bug in the mover]

1 minute ago, trurl said:

Krusader renamed the files to another path on the same disk, so they stayed on the same pool they were on before the move.

 

Mover only moves from the designated pool. That is by design.

 

Krusader works as expected. This is not the issue!

 

The issue is what you describe a design choice.

 

Why not let the mover move from all pools and not just the designated one? No harm in that I (naively) assume?

 

Please don't brush it off and take it under consideration. Thank you!

[I think I found a bug in the mover]

5 minutes ago, trurl said:

Not really a mover bug. Linux (Krusader) didn't actually move the files to another disk, it just renamed them to a new path on the same disk. See #2 here:

 

I never expected Krusader to move the files to another disk. I went with Krusader into the Share UNRAID/user/downloads and moved them to the Share UNRAID/user/media. I expect the mover to do the moving between disks.

 

Unraid knows the files are on a cache pool. The mover just does not check every cache pool to move files just the one set in the share as the designated cache.

 

Respectfully if it's not a bug it's an oversight that should be fixed

[I think I found a bug in the mover]

Scenario is this. I have two shares, "Downloads" and "Media". I also have two cache pools, "Download" and "Cache".

The cache pool for the Share "Downloads" is "Download". The cache Pool for the Share "Media" is "Cache".

 

After I downloaded files to the "Downloads" share via the "Download" cache pool I move the files via Krusader to the Share "Media".

 

Now when I invoke the mover the files in the Share "Media" and on the Cache Pool "Download" stay on the Cache Pool "Download". Only after I change the Cache Pool of the Share "Media" from "Cache" to "Download" the mover takes action.