I am testing a restore of a v14 Fileserver appliance (with some extra packages) to a v15 Fileserver. The backup is approx 80GB, managed by the HUB. Target is an AWS t2.medium instance with 600GB storage.

After more than 36 hrs tklbam-restore seems stuck. The last lines in the log show 

  chown -h www-data:www-data /var/www/ajaxplorer/data/plugins/auth.serial/jacob
  chown -h www-data:www-data /var/www/ajaxplorer/data/plugins/auth.serial/root
  chown -h www-data:www-data /var/www/ajaxplorer/data/tmp/update

Enhough disk space available

root@fileserver /# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            2.0G     0  2.0G   0% /dev
tmpfs           396M   43M  353M  11% /run
/dev/xvda2      550G  287G  242G  55% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup

But tklbam-restore is still hogging cpu

top - 10:20:56 up 1 day, 15:03,  3 users,  load average: 1.20, 1.06, 1.02
Tasks: 123 total,   2 running, 121 sleeping,   0 stopped,   0 zombie
%Cpu(s): 37.9 us, 12.1 sy,  0.0 ni, 49.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.2 st
KiB Mem :  4049088 total,  1856228 free,   282844 used,  1910016 buff/cache
KiB Swap:        0 total,        0 free,        0 used.  3457636 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 1433 root      20   0  255432  70180   3588 R 100.0  1.7   2317:00 tklbam-restore
  765 root      20   0  213680  15800   6312 S   0.3  0.4   0:35.99 fail2ban-server
 5003 root      20   0   41332   3388   2732 R   0.3  0.1   3:44.81 top
    1 root      20   0   57488   7192   5304 S   0.0  0.2   0:04.15 systemd

IO and network traffice only spiked first few hours and are almost zero now.

What is keeping tklbam-restore so busy? Why hasn't is finished or errored? What else can I check?