Hello,

very often, the "fix common problems" plugin tels me I have data on a pool that's not supposed to be there. and therefor, it won't end on the array or the right pool.

 

what I would like is, in the share settings, to be able to set the primary storage as a wildcard, meaning, where ever the file is, it will end up on secondary storage at next move.

Primary is where new files are written. Obviously this makes no sense as a wild card.

 

Secondary is where files overflow if Primary gets below Minimum Free.

 

A more flexible setting for Mover Action has been discussed.

 

sometimes, shares are on different pools. when copying data, files could be written on wrong pool (because it's just a share anyways). so wildcard would be great.

Best exemple a data share with a pool and a backup share with it's own pool...

 

All I would need is that mover put's the file where I ask him to no matter where it was.

I'll have a look at the discussion.

thanks

Edited January 17, 20242 yr by Nexius2

8 hours ago, Nexius2 said:

when copying data, files could be written on wrong pool

Do you mean moving instead of copying? If you try to move from a share on one pool to a share on another pool, it is possible for Linux to just 'repath' the files to the same pool they were on. See the Caution in the Overview section of the Documentation on User Shares:

https://docs.unraid.net/unraid-os/manual/shares/user-shares/

 

Dynamix File Manager will avoid this problem because it always does move as copy to destination then delete from source.

 

On the other hand, if you really mean copy to a share, and you think it has written files during that copy, to a pool other than the designated pool, then you are mistaken. It only writes to Primary.

 

If it is replacing files in the share that already exist on some disk or pool, then the file is replaced where it already exists.