Good Evening,

 

I have done a bit of homework and I have successfully moved at least 10 gigs off my cache drive. However, it seems the Docker and libvirt.img files seem to be holding me up. 

 

My end goal here is to delete the cache drive all together. When I first built this system I was using mechanical drives but moving forward they are being replaced with larger SSD's so the need for a small cache SSD is redundant. My setup would be much more optimized with the extra slot for an extra drive to add to storage.

 

I have located information regarding stopping the docker and VM services through settings. I then went into my System and AppData shares and have changed the cache option to "Yes" research indicates that this should migrate the data from the cache drive to the arrays once the "Mover" process has been invoked.

 

That has not been my experience though. Am I missing something in the new 6.7 version? Is there easier ways to do this? Please keep in mind my Linux exposure although adequate, is limited and leaves me dangerous clunking around through this thing. 

 

Any detailed and grade school instruction in this area is much appreciated.

 

Additionally if the answer is, "Chill out Francis, These are large files and are probably going to take some time" I will not be offended!

 

Thank you in advance!

Edited April 7, 20197 yr by RogueWolf33

Chill out Francis, These are large files and are probably going to take some time - Actually depending upon the containers you were running, the appropriate answer would be

 

Chill out Francis, these are small files and there are hundreds of thousands of them and this will take some time.

 

 

If you want to see the progress, enable Mover logging in settings - Scheduler - Mover Settings, then open up the syslog window and run Mover from the main tab

 

Edited April 7, 20197 yr by Squid

1 hour ago, Squid said:

Chill out Francis, These are large files and are probably going to take some time - Actually depending upon the containers you were running, the appropriate answer would be

 

Chill out Francis, these are small files and there are hundreds of thousands of them and this will take some time.

 

 

If you want to see the progress, enable Mover logging in settings - Scheduler - Mover Settings, then open up the syslog window and run Mover from the main tab

 

 

Awesome! I Love logging! Thank you for the tips!

 

This is what I got:

 

shareMoverSchedule=40+3+*+*+*&shareMoverLogging=yes&changeMover=Apply&csrf_token=****************
Apr 6 21:00:24 Tower emhttpd: shcmd (443): /usr/local/sbin/update_cron
Apr 6 21:01:24 Tower emhttpd: req (6): cmdStartMover=Move+now&csrf_token=****************
Apr 6 21:01:24 Tower emhttpd: shcmd (446): /usr/local/sbin/mover |& logger &
Apr 6 21:01:24 Tower root: mover: started
Apr 6 21:01:24 Tower move: move: file /mnt/cache/system/docker/docker.img
Apr 6 21:01:24 Tower move: move_object: /mnt/cache/system/docker/docker.img File exists
Apr 6 21:01:24 Tower move: move: file /mnt/cache/system/libvirt/libvirt.img
Apr 6 21:01:24 Tower move: move_object: /mnt/cache/system/libvirt/libvirt.img File exists
Apr 6 21:01:24 Tower root: mover: finished

 

 

This doesnt sound like it's moving to the array. Unless it's already there and it doesn't actually remove the old file? Or maybe somehow I jacked it up and got a partial one moved over which is very possible I guess....

 

Any feedback would be appriciated. Thank you!

Yup both are on the array already. Am I safe to remove the cache and see if my dockers come up?

 

Update: Nope... Dockers still dont come back when I remove the cache from the array. this leads me to believe these .img files may be incomplete possibly?

Edited April 7, 20197 yr by RogueWolf33

You're always actually safe to remove docker.img (its very easily recreated).  But I would remove the one from the array and then move it again (because if you're referencing /mnt/user/system/docker.img for the path, then it's actually going to use the version (when there's 2) from the cache drive

 

rm /mnt/user0/system/docker/docker.img

 

will get rid of the array version.

 

Similarly for the libvirt image  (And that is not so easy to recreate if there's a problem with it - assuming you're using VMs - if you're not, then don't worry about that file at all)

Edited April 7, 20197 yr by Squid
path mistake

4 minutes ago, Squid said:

You're always actually safe to remove docker.img (its very easily recreated).  But I would remove the one from the array and then move it again (because if you're referencing /mnt/user/system/docker.img for the path, then it's actually going to use the version (when there's 2) from the cache drive

 

rm /mnt/user0/system/docker/docker.img

 

will get rid of the array version.

 

Similarly for the libvirt image  (And that is not so easy to recreate if there's a problem with it - assuming you're using VMs - if you're not, then don't worry about that file at all)

nope, No VM's just dockers. ill let you know how it goes! Here's mud in yer eye!

 

At first, I thought it didnt delete. Minor detail though 22.6 GB is much different from 22.9 MB

 

Last component. Anything fancy I have to do to be rid of cache drives all together? As in, do I disable it somewhere?
 

Thanks so much for your help with this!!!

Just unassign them in the drop down when the array is stopped (main tab)

3 minutes ago, Squid said:

Just unassign them in the drop down when the array is stopped (main tab)

Fabulous,

 

Everything has worked perfectly. Thanks again for the direction Squid! Remind me to buy you a puppy or something! Last question, Should I disable the mover logging as a best practice tactic? I think my USB boot drive has plenty of room for logs but I don't want to degrade system performance either.

Nevermind. I disabled it. There is no need for mover logging since there is no Cache! Thanks again for all of your help!