Hello,

 

I have the problem, that when I switch shares to "prefer cache", the mover will do nothing. Mover tuning was uninstalled for testing. There is plenty of space in the cache drive (700GB free, around 100GB should be moved from the array to cache).

Is there anything I'm missing?

Is it a problem that the cache drives were added later? If so, how can I get the mover to transfer it anyway?

 

Thanks in advance

Edited April 11, 20215 yr by TGP

 

9 minutes ago, TGP said:

Is it a problem that the cache drives were added later?

This is not a problem - in fact it is one of the purposes of the 'prefer' setting.

 

Note that open files cannot be moved so you may need to temporarily disable the docker and/or VM services if they are holding open files you want to be moved.

 

You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.  You could also try enabling mover logging to see if that giver a clue.

VM's and Docker Services are disabled. The files are also not associated with it.

The mover log shows just that it immediatley stops, without further information.

 

My next step would be creating a new share in the cache and rename it as the old one...

tgp-nas-diagnostics-20210411-1245.zip

Edited April 11, 20215 yr by TGP

The diagnostic's show that the Mover Tuning plugin IS installed and other posts suggest it seems to be causing a lot of people problems  

 

I would suggest uninstalling the plugin, recreating the issue; and posting new diagnostics.

I  reinstalled it meanwhile. I removed it and tried again, there was no difference. I even rebooted the server after uninstalling. But I can repeat the steps if it helps.

Next try without plugin. Nothing happened. Also curious: When I try to use "ls" in the terminal, nothing shows up.

tgp-nas-diagnostics-20210411-1312.zip

Edited April 11, 20215 yr by TGP

9 minutes ago, TGP said:

I  reinstalled it meanwhile. I removed it and tried again, there was no difference. I even rebooted the server after uninstalling. But I can repeat the steps if it helps.

 

There was no mover logging in the last diagnostics posted - not sure if the plugin interferes with that and without that it is hard to guess what might be going wrong.  The last diagnostics show mover logging NOT enabled so you might want to check that as well.

 

Might have to wait to see if anyone else has any idea  

Interestingly enough only shares with Windows imagebackups and filehistory  are affected.

3 minutes ago, TGP said:

Interestingly enough only shares with Windows imagebackups and filehistory  are affected.

I must admit that I can not think of any reason that should be the case.   Not sure why you would want imagebackups on the cache in the first place

 

I was thinking that a share anonymised as M....a might be a Media share that was having these problems?  

Enable mover logging, run the mover, post new diags.

The media share works perfectly fine. I keep images of testmachines in the cache for quicker imageupdates and access.

Nothing to see in the log, as far as it shows up correct to me.

tgp-nas-diagnostics-20210411-1331.zip

According to the mover log there's nothing to be moved, from what share are you trying to move data?

It is called TGP Backup. I just made a new one and copy the files over. I don't know why the mover does not recognize those files.

Edited April 11, 20215 yr by TGP

It's a bug, mover isn't working for shares with a space in the name, you should create a bug report.

 

As a workaround you can rename the share, using for example an underscore.

Note it's only not moving from array to pool, it still does from pool to array, even with a space in the name.

Thank you for your help. I would have ran into the same issue with cloning the share. Problem should be solved with renaming.

1 hour ago, JorgeB said:

It's a bug, mover isn't working for shares with a space in the name, you should create a bug report.

 

As a workaround you can rename the share, using for example an underscore.

@JorgeB can you see if this fixes it: (and doesn't cause any other issues - It shouldn't)

 

Save the attached as /usr/local/sbin/mover  (and give it executable permissions)

 

mover

I just renamed everything and it works as intended. I have some time tomorrow to test it out. A bugreport is also created.

18 hours ago, Squid said:

 can you see if this fixes it:

It does appear to fix it.

On 4/11/2021 at 3:40 PM, Squid said:

@JorgeB can you see if this fixes it: (and doesn't cause any other issues - It shouldn't)

 

Save the attached as /usr/local/sbin/mover  (and give it executable permissions)

 

mover 4.07 kB · 7 downloads

I had a similar issue with appdata for containers. this solved it for me, moved everything i was expecting.

 

so THANK YOU! 

 

Does still seem to have an issue with .folderd (.icons in my case). Not an issue for me since those will be deleted anyway, but perhaps good to know. 

 

I see errors like:

May 3 14:23:30 Zorby move: move: file /mnt/disk1/appdata/binhex-preclear/home/.icons/BLACK-Ice-Numix-FLAT/scalable/actions/reply-rtl-symbolic.svg
May 3 14:23:30 Zorby move: move_object: /mnt/disk1/

 

Upon checking these files do actually exist. 

The bug is still not fixed.

I am using 6.11.0-rc4, its fine moving files from cache pool to the array with a space in the share name.

But after replacing the Cache drive i cannot move the files back.

Mover starts and finishes instantly.

Renamed the share with out a space and mover started moving files to the new cache drive.

 

Will submit a bug report