[6.9.0-beta35] Multi-pool and mover issues

This is the way it is designed to work, and some people depend on it working that way. No and Only shares are ignored by mover.

 

 

You are describing correct behavior as it was designed.  If you want to change a share from cache 'yes' to cache 'no' and have files moved off cache pool, you should first invoke mover (Move Now button) to move all those files and then change Use cache config from 'yes' to 'no' so that future new files are written only to array.

 

Having said that, I can see how this can be unexpected behavior depending on how you interpret the config settings.  Current use of the 'mover' is pretty simple, but the functionality exists to add quite a bit more sophistication.  This is a "future feature" item

Changed Status to Open

Changed Priority to Other

I understand that it might be designed that way, but that doesn't mean it's correct. I only discovered that because I tried to write my custom mover scheduler, otherwise I would found out it the hard way with no space left in pools.

 

At the very least this should be explained better in tooltips.

14 minutes ago, Tomr said:

At the very least this should be explained better in tooltips.

There is Help in the webUI. The Help (?) icon on the main menu bar toggles help on/off for the whole webUI. Also, most settings will toggle help by clicking on the label for the setting.

 

While I agree that the terms used can be interpreted different ways and could be clearer, the details given in the UI are quite clear once you take your time looking at it.

 

Clicking on the text shows a clear explaination AND the result of the selected choice is stated on the right.

Ok, made almost the same post.  

They don't state that the files will be orphaned if the setting are changed, or the whole things with hardlinks. And I was assured that would work as I expected because of this:

15 minutes ago, Tomr said:

They don't state that the files will be orphaned if the setting are changed,

They are not orphaned in the sense they become invisible.  No matter what settings of Use cache, all files across all disks/pools will be shown for a share.

 

15 minutes ago, Tomr said:

whole things with hardlinks

All that means is: if you have a hard link to a file, when that file gets moved, the hardlink also gets moved in the sense that it gets created in the destination.  So if you have:

 

/mnt/user/myshare/file

/mnt/user/myshare/hardlink-to-file

 

and file and hardlink-to-file is on say, 'cache', then when file is moved to array, whatever disk it ends up on we also create on that disk hardlink-to-file.