display error

Using the CA Mover tuning:
Are the following folder automatically excluded, if "Free down/prime up to this level of used Primary (cache) space:" is set to `0%`?
- appdata
- domain # VMs

- system # Docker

ideally those shares would be set to use cache only and never be touched by the mover.

Mover tuning will not touch them if the shares are configured not to use secondary storage.

14 hours ago, p0p said:

Are the following folder automatically excluded,

nothing is automatically excluded

21 hours ago, droid said:

 

display error

I'm getting the nearly the same...numbers listed from 1 to 1000 (each a new line). Mine are fully left-aligned whereas yours seem to be nested under the "Move files that are...: 

 

does it do it in every browser you try?

 

perhaps there is an issue with the theme you are using, or some browser plugin (an ad blocker trying to block scripts for example?)

I reinstalled and switched browsers but nothing worked

22 hours ago, Shu said:

I'm getting the nearly the same...numbers listed from 1 to 1000 (each a new line). Mine are fully left-aligned whereas yours seem to be nested under the "Move files that are...: 

 

I reinstalled and switched browsers but nothing worked

I'm getting the same numbers carrying on forever. I'm running it on unraid 6.11.5. 

I still can't get it to ignore files in a list either on the newest build. 

Same here, ignoring files doesn‘t work. (7.0.0-beta4)

when running beta are you replacing unraid beta mover file with the plugins mover file?

its noted in earlier in the forum as well:

 

Edit your go file at: /boot/config/go and add:

rm /usr/local/sbin/move

ln -s /usr/libexec/unraid/move /usr/local/sbin/move

 

Symlinks should not be necessary with the current version of the plug-in, that was fixed quite a while ago.

 

On 11/21/2024 at 1:27 PM, droid said:

I reinstalled and switched browsers but nothing worked

 

I can see the line in the code that is definitely causing it, but I don't know why that one is behaving differently to the age drop-down that works.. PHP is not my thing, my web dev experience started and ended with HTML4.

Unless its sensitive to the line break and tabbing in the .page file and that's somehow breaking it out of the <select> tags its in?

That's the only difference, and I didn't think any of that mattered for html, but I guess .page files for unraid are handled a little differently?

 

we might have to wait for a proper dev to get back onto this project. @Reynald has been away (he was moving house, then had some hardware failures etc)

 

I cant get my systems to render it wrong though, it all works fine on every machine and browser I have.

16 hours ago, Faceman said:

 

I can see the line in the code that is definitely causing it, but I don't know why that one is behaving differently to the age drop-down that works.. PHP is not my thing, my web dev experience started and ended with HTML4.

Unless its sensitive to the line break and tabbing in the .page file and that's somehow breaking it out of the <select> tags its in?

That's the only difference, and I didn't think any of that mattered for html, but I guess .page files for unraid are handled a little differently?

 

we might have to wait for a proper dev to get back onto this project. @Reynald has been away (he was moving house, then had some hardware failures etc)

 

I cant get my systems to render it wrong though, it all works fine on every machine and browser I have.

alot of theses sym link error and issues are in the unraid v7 beta and was recorded around beta 2 and still a problem in beta 4.

not sure of a proper fix but the symlink it the fix for many issues in the beat version. Not a problem in stable 6. may not be a problem in stable 7 when realse.

yes emhttp has a different in how html/php is render in ther ".page" file Your correct, just reviewed and saw that in beta on my production machine... it may be breaking out of the html tag. but that shouldn't stop mover in terminal form breaking the way it does and has been reported... htop and other captures mover still trying to move but never completing.

Again, for BETA only... has 

rm /usr/local/sbin/move

ln -s /usr/libexec/unraid/move /usr/local/sbin/move

*this been the fix for me and others.

other say its the plugin on beta which is why i decide to post here again to see if the dev can take another look.

I was specifically referring to the number rendering issue on the configuration page in that post, it looks correct but the only difference between that drop down and the others is some extra tabbing and line breaks in the .page code, which I assumed wouldn't change how it is interpreted, but some peoples browsers are getting tripped up by it. suspect line is HERE.

 

The symlink for the mover script issue has never affected me, I've been on beta since the first public version and mover tuning fixed it a few days after release by adding the correct symlink to the plugin script. i'm currently on 7.0.0beta4

 

 

I had to uninstall this plugin because it kept breaking docker. It seemed to be ignoring my preference to have docker and other shares on cache. Not sure if this is expected behaviour and I haven’t had time to look it up. Priority was getting docker back on cache so it can start

I'm running into an issue with this plugin, I assume, not correctly escaping a "space" in my "TV Shows" share name, thus producing an error (see attached). I searched for this topic and found some others who have experienced similar issues recently with "special characters". The advice given seems to be renaming shares or filenames, which frankly is not an option I'd like to consider at this point - primarily due to breaking other functionality.

 

Is there really no other solution than re-naming shares/folder/filenames? I've used older iterations of this plugin that did not have the same problem, so I'm just curious what may have changed that would be causing this. I'm very appreciative of the functionality this plugin can provide, so I hope there are alternative solutions to this issue. Many thanks!

43 minutes ago, cinsun42 said:

so I hope there are alternative solutions to this issue. Many thanks!

rewriting some code parts  ... im sure @Reynald will look into it once he has some time.

 

btw. "special characters" and spaces are always not a good Option as note as they pretty often are interpreted as "funtion" ... but yes, a space shouldnt be too hard to solve

 

and about renaming, a simple TV_Show (underscore instead space) helps already ... and almost looks the same

38 minutes ago, alturismo said:

and about renaming, a simple TV_Show (underscore instead space) helps already ... and almost looks the same

 

Is it just the share name, or would it need to be all underlying files and folders as well?  I think I can probably handle making an adjustment to the share name and re-directing all related dockers/plugins, but if files/folders need the same its sort of a non-starter

1 hour ago, cinsun42 said:

Is it just the share name, or would it need to be all underlying files and folders as well?

good question, usually i would say ... hmm, but overall i asume most users will have Media file with spaces ... so most users should have issues overall ... may just give it a try in a quick test.

 

im using my own mover here, so cant tell for sure.

confused over some massive work mover is doing... when not really necessary ... Hope its not damaging anything...

 

I recently installed mover tuning... but did not really mess with it too much.

 

seems to be moving various appdata files to user0. What does it mean?

 

log is getting spammed with this...

 

>>

Dec 5 23:05:41 buckyu move: 150466 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03877-capture.jpg" to /mnt/user0/

Dec 5 23:05:41 buckyu move: 150465 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03878-capture.jpg" to /mnt/user0/

Dec 5 23:05:41 buckyu move: 150464 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03879-capture.jpg" to /mnt/user0/

Dec 5 23:05:41 buckyu move: 150463 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03880-capture.jpg" to /mnt/user0/

Dec 5 23:05:41 buckyu move: 150462 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03881-capture.jpg" to /mnt/user0/

Dec 5 23:05:41 buckyu move: 150461 files remaining from caches to array 640GiB

Dec 5 23:05:41 buckyu move: Moving "/mnt/cache/./appdata/Zoneminder/data/events/2/2024-07-18/8/03882-capture.jpg" to /mnt/user0/

>>

 

I rebooted to interrupt this behaviour. Appdata seems fine as far as I can tell... it seems to be moving files to nowhere... and taking a long time doing it.

 

I have appdata defined at primary/cache  secondary/array mover array/cache.

 

I really dont understand this.... any hints are appreciated.

 

 

20 hours ago, alturismo said:

good question, usually i would say ... hmm, but overall i asume most users will have Media file with spaces ... so most users should have issues overall ... may just give it a try in a quick test.

 

im using my own mover here, so cant tell for sure.

So I did end up making the change to only the share name ("TV Shows" to "TV_Shows") and it seems to work with all underlying files! Many thanks!

 

Now I have a follow up question. I did a trial run in test mode and without going into all the details it definitely looks like it wants to move the files I most recently moved onto my cache pool, instead of the much older (up to 3 months) worth of data. I'm talking about things that have been moved onto cache within the past week. I'm using the 'Auto' setting for moving files based on age. Any thoughts why this would be happening? I was expecting the opposite behavior

 

EDIT: I think I've answered my own question. Many of the files don't have recent modification dates, despite being transferred recently. I'd probably need to make more deliberate attempts to re-name files (or similar) to reset the modification date.

Edited December 5, 20241 yr by cinsun42

28 minutes ago, cinsun42 said:

EDIT: I think I've answered my own question. Many of the files don't have recent modification dates, despite being transferred recently. I'd probably need to make more deliberate attempts to re-name files (or similar) to reset the modification date.

exactly, a simple

 

touch /blabla/file name here.xyz

 

will do it  no renaming needed

Is there a way to use this plugin to force any contents of a specific directory to be moved?

 

I like the idea of allowing some recently created files to sit on the cache, speed up access, etc, which this plugin seems to allow (using filter threshold percentages). But there's a directory in my share that gets large files added regularly, which can be moved straight off cache into the array. They're backups, and won't be accessed again for weeks or months. So I'd like the mover to move those always, and then maintain a % buffer in the cache of recent files.

 

I suspect the way it's written wouldn't really allow this, and I almost need 2 different mover configurations. One that just moves the backups, and one that then manages the remaining files at the desired threshold %.

2 hours ago, froggles said:

But there's a directory in my share that gets large files added regularly, which can be moved straight off cache into the array. They're backups, and won't be accessed again for weeks or months. So I'd like the mover to move those always, and then maintain a % buffer in the cache of recent files.

if its a seperate share ... yes

 

inside the share settings, scroll a little down

 

 

would always move like without mover tuner ...

 

Edit, sorry, there you set your individual settings for this Share ...

Unfortunately it's the same share, and I don't think it's sensible to split up (the backups are previous versions of large files, moved when new versions are created, so don't want to have the innefficiency of copying them across to a different share when this occurs). So I don't think this works?