odd, I provided extensive info in my opening post, but somehow I cannot see that anymore. Well, here we go again:

I have a v14 fileserver appliance (with some mods), running on bare metal. I intend to replace my server, and upgrade to v15 fileserver on VMware. The backup is approx 80GB. I want to test the procedure first, so I started ant2.medium instance on AWS, with 600GB HDD. The tklbam-restore has been running for over 36 hours now. Afer peaking the first hours, now showing very little IO or network activity.

last lines in /var/log/tklbam-restore

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

 

output df -h

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

 

tklbam-restore keeps hogging cpu

 

top - 16:40:36 up 1 day, 21:23, 3 users, load average: 1.00, 1.00, 1.00

Tasks: 123 total, 2 running, 121 sleeping, 0 stopped, 0 zombie

%Cpu(s): 37.9 us, 12.0 sy, 0.0 ni, 49.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.2 st

KiB Mem : 4049088 total, 1892076 free, 275680 used, 1881332 buff/cache

KiB Swap: 0 total, 0 free, 0 used. 3462884 avail Mem


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

1433 root 20 0 255432 70180 3588 R 99.7 1.7 2696:39 tklbam-restore

652 stunnel4 20 0 579080 6812 4448 S 0.3 0.2 0:01.60 stunnel4

667 shellin+ 20 0 37456 3316 2552 S 0.3 0.1 0:00.30 shellinaboxd

5003 root 20 0 41332 3504 2732 R 0.3 0.1 4:21.04 top


Why is tklbam so busy? What is it doing? Why doesn't it finish or throw an error? What else can I check?