Hi,
Running 6.9.1.
I have some repeatable behavior that I can't explain and I would appreciate your input.
I typically run my appdata, system and domains shares with cache set to prefer.
I recently decided to move all these shares back to the array in preparation for some work I am doing, so I followed the wisdom of the FAQ, stopped docker and vms in settings, changed my shares to Cache:Yes and ran the mover.
It ran for a while and moved almost all the data from the cache to the array. However it did not totally empty the cache.
There are a few "files" remaining. The cache reports it has ~3.5G still in use.
I have had a poke around. and the issues seem to be related to files belonging to the following dockers
letsencrypt
binhex-krusader
swag
My first observation is that the space calculation seems weird as there are a lot less "files" in there than 3.5GB.
If I take swag as my example I notice that this docker makes use of symlinks.
So the problem path for swag is a broken symlink that does not exist.
root@cosmos:/mnt/cache/appdata/swag/keys# ls -l
total 0
lrwxrwxrwx 1 nobody users 38 Mar 15 21:31 letsencrypt -> ../etc/letsencrypt/live/obfuscated-domain.co.uk
When I go and poke into the other problem dockers they also all seem to have broken symlinks.
So these 3 "problem" dockers all make use of relative symlinks in their docker volumes.
So my question is this. Does the mover copy symlinks as links? Or does it follow links?
It looks to me like maybe it is trying to follow links, but as the target has already been moved.
This is backed up my the fact that the target that the symlink points to exists on the array. (not that that really matters a broken symlink should be copied as a broken symlink anyway, even if the target does not exist)
It has broken the dockers involved here (not that i really care, I can sort them out), but I am worried that the mover seems to be struggling with relative symlinks. between the cache and the array.
If I use Unbalance plugin, or use rsync myself then the move works as I would expect.
Anyone else seeing this or anything like it?
Thanks in advance for your time and efforts.
Diags attached for your grepping pleasure.
UPDATE: Exactly same behaviour when using the mover to get back onto the cache, same 3 dockers, same issues with symlinks.
cosmos-diagnostics-20210319-0912.zip