Looking at the logs while the mover is working, there is endless scrolling of the mover being unable to move files to a non-existent folder in user0.  I opened the file manager and sure enough, the folder it's trying to move to is not there.  It's in user but not user0.

 

I connect to the share and see the folder and files there. But am I looking at the files in the cache and not really on the array?

 

I did change the way the cache moves a few days ago but never noticed any file loss or anything.

 

Should I be concerned?

Attach Diagnostics to your NEXT post in this thread.

I think I figured it out.    I had that share set to cache only for a few days and then I added a new sharedrive, set the cache to THAT drive before moving the old cache to array.

 

I think I created orphaned files that never moved until I forced it.

 

I assume I can manually just move them to where I want them to go one of the array drives and then just run parity with fix and be all good?

 

thanks for the reply.

 

Not entirely clear what you did, but no need to run parity after manually moving. Parity is always updated at the same time as any array writes.