hugenbdd

I'm starting to work on a seperate script for this. Once I release it, I'll post a new forum thread separate from Mover Tuning. At first it will just move based on age of files (oldest first). I would expect later it will include other filters from Mover tuning.

If I wrote this, it would be an independent script and not part of the plug-in. But this could be done as a cron entry.

Looking for a few to test the changes above before I release. Just replace the age_mover file with the one attached. /usr/local/emhttp/plugins/ca.mover.tuning/age_mover age_mover

I would need to see Logs.

I'm not able to reproduce. I'm willing to do a google meeting sometime next week if you want me to look at it.

I'll have a fix in the next few days addressing. 1.) The echo statements in the hardlink section. 2.) Moving empty folders. 3.) Fix a "testing" if statement in the hardlink section of code.

I left a few echo's in there. I'll move them to the mover logs under /tmp/Mover on the next release. If you need it removed before the release, you can just comment out (#) the echo's in age_mover file.

Yes, I'm purposely skipping them for this release. I will be including them in the next release.

Can you DM the log file in /tmp/Mover/ Mover_Tuning_<DATE/TIME>.log as most entries are no longer in the syslog. I have not changed this part of the code and can't determine what's going on without more info.

2023.05.23 Fixed Hardlinks issue. If hardlinks detected in fileslit. No GUI update is available. No Soft Stop available.

TY, I will put a release out first thing in the morning.

File attached fixes the hardlinks issue but will not give status updates or soft stop. replace the file below with the attached file. Once someone is able to test I will package it up in a new release. /usr/local/emhttp/plugins/ca.mover.tuning/age_mover age_mover

I have a fix I'm testing now.

Not yet but this will enable us to write the code for that. With the original find, it just sends the full output to the binary mover. With a file list, we are able to manipulate it any way we want before we send them to the mover.

Thanks For those with hardlinks. I would suggest to pause or not move the script for a few days while I work on this. I have to recreate how the binary mover handles hardlinks. (i.e. tracking inodes and how to handle them in the filelist)

Can you DM logs from /tmp/Mover and also from syslog? I don't know why hardlinks would be any different than a normal file. It's using the same find that the old mover is, it's just that it's sending it to a filelist file. Then I loop through a filelist and send each file to the binary mover. (I wonder if it's moving on to the next file and starting a new file before the previous is done.). I might need to check and see if any "mover" is still running before moving forward...)

Moved to a filelist based system instead of sending the find output to the mover binary. The first release of this had an issue with some special characters in the file name. But that was fixed Thursday.

Few questions. 1.) Did you install the update I released yesterday? 2.) Can you send me some of the files (in a DM) that are under /tmp/Mover 3.) what version are you on?

Yeah, right now I'm specifically excluding them. But I guess I shouldn't. Next release I'll move empty folders.

###2023.05.18 - Fixed a issue where SED was seeing [] and {} inside of the filepath string, by double quoting the echo'd variable. - Added softstop as a command to gracefully exit the mover from the command line. Checks for a (empty) file under /var/run/moversoft.stop before sending each file to the binary mover. Will exit the loop if the file exists and mover will stop once the current file is done moving. This is more graceful than the original stop (Which still exists) that just kills the PID. Example: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover softstop

I'll have an update out this afternoon to fix it.

I have an updated file. It appears because I didn't " the variable in the echo statements that the } and [ in the names interacted with the SED statement. First time I have run into something like that. I have a file with it fixed and it works on my limited testing. Going to try and put a release out tomorrow, but if you want to test you can update the age_mover file. age_mover.txt

I think a fix for Jay's issue and it might also fix yours. However, the forum is slow/down so I can't send it over to him to test. no it's not intended.

Sent you a DM asking for some files. I believe this has something to do with the naming of the files and not just the spaces. (Maybe special characters, not certain yet)

Yup, looks like a bug. I'm surprised I haven't run into this on my box as I do have spaces in files. Are you on the latest Mover Tuning release and what version of unRAID?