Bug with Pools? Am I missing something?

[TDD]

Hi all.  Let's see if we can make this clear.

 

1) I have three pools.  My 'storage' pool is my scratch disk where I do many intermediate things with files.  It used to be set up under unassigned devices but for future data protection, it is pooled now in case I want the system to move its contents onto the array.

 

 

2) Within 'storage', I have a 'Downloads' folder, and many folders in that.  In this case, I am focused on '@Converted'.  It is where my manual transcoding of video files end up rather than overwriting originals.

 

 

3)  Any files in @Converted that I choose to move onto the array via Midnight Commander (via SSH shell...) from '/mnt/user/Downloads/@Converted' (the contents of 'Storage' of course get exposed as shares) to '/mnt/user/TV/xxx' (my intended destination) end up as a new share on 'Storage' rather than on the array (or very least, the cache)

 

 

4) This is unexpected behavior since the TV share is set to 'cache' pool.

 

 

I would expect the copy to /mnt/user/TV from 'Storage' to arrive at 'cache' for mover transfer later.

 

Should I be expecting that all pool devices just maintain a 1:1 relationship with the array according to any share's particular pool settings?

Will the mover move, according to these settings (it should) data to/from the array into the relevant pools as needed?

 

Maybe I am just stuck on old thinking that the cache pool itself was special and now we have just broadened it all out.

 

 

Kev.

[SimonF]

8 minutes ago, TDD said:

Hi all.  Let's see if we can make this clear.

 

1) I have three pools.  My 'storage' pool is my scratch disk where I do many intermediate things with files.  It used to be set up under unassigned devices but for future data protection, it is pooled now in case I want the system to move its contents onto the array.

 

 

2) Within 'storage', I have a 'Downloads' folder, and many folders in that.  In this case, I am focused on '@Converted'.  It is where my manual transcoding of video files end up rather than overwriting originals.

 

 

3)  Any files in @Converted that I choose to move onto the array via Midnight Commander (via SSH shell...) from '/mnt/user/Downloads/@Converted' (the contents of 'Storage' of course get exposed as shares) to '/mnt/user/TV/xxx' (my intended destination) end up as a new share on 'Storage' rather than on the array (or very least, the cache)

 

 

4) This is unexpected behavior since the TV share is set to 'cache' pool.

 

 

I would expect the copy to /mnt/user/TV from 'Storage' to arrive at 'cache' for mover transfer later.

 

Should I be expecting that all pool devices just maintain a 1:1 relationship with the array according to any share's particular pool settings?

Will the mover move, according to these settings (it should) data to/from the array into the relevant pools as needed?

 

Maybe I am just stuck on old thinking that the cache pool itself was special and now we have just broadened it all out.

 

 

Kev.

Mover will only move from pools to array or array to pool but not between pools.

[TDD]

As I thought with mover - good to confirm.

 

I can't actually manually move the files onto the array as the system fuses the newly created TV share as part of the physical array share.  And I don't want the mover to move them.

 

It would seem that my only escape is to make the Storage device an unassigned one to detach it from any attemps to meld shares...

 

Kev.

[itimpi]

21 minutes ago, TDD said:

3)  Any files in @Converted that I choose to move onto the array via Midnight Commander (via SSH shell...) from '/mnt/user/Downloads/@Converted' (the contents of 'Storage' of course get exposed as shares) to '/mnt/user/TV/xxx' (my intended destination) end up as a new share on 'Storage' rather than on the array (or very least, the cache)

If you are using move rather than copy/delete then you are probably encountering the behaviour described here in 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.

[TDD]

TY for this - I somehow glossed over that part of the docs - despite using the sysytem for years 🙂

 

I will rethink how that particular pool drive is set and whether I disassociate it via UD or make it loosely attached to the array.  I only really brought it in as a pool drive as it is BTRFS and I like the nifty GUI tools that support the file system.

 

Kev.

[primeval_god]

On 12/6/2022 at 3:00 PM, TDD said:

TY for this - I somehow glossed over that part of the docs - despite using the sysytem for years 🙂

 

I will rethink how that particular pool drive is set and whether I disassociate it via UD or make it loosely attached to the array.  I only really brought it in as a pool drive as it is BTRFS and I like the nifty GUI tools that support the file system.

 

Kev.

The only thing you really need to change is your copy command. Instead of doing '/mnt/user/Downloads/@Converted'  -> '/mnt/user/TV/xxx' do '/mnt/Storage/Downloads/@Converted'  -> '/mnt/Cache/TV/xxx' copying from disk share to disk share. Just be sure not to do copies between disk shares and user shares.

[TDD]

Yea - I can do the disk <-> disk level transfer, but then I have to see which disk will accommodate the transfer.  Not a big deal, but likely my out.  I really try to keep my work under /mnt/user and let the system do the allocations, but in this edge case, of course not.

 

Kev.

[itimpi]

6 hours ago, TDD said:

Yea - I can do the disk <-> disk level transfer, but then I have to see which disk will accommodate the transfer.  Not a big deal, but likely my out.  I really try to keep my work under /mnt/user and let the system do the allocations, but in this edge case, of course not.

 

Kev.

If you transfer the files to the pool that is set to cache the TV share then the mover will later move them to the array distributing them according to the settings for that share.