MyData.tgz size and filetool.lst occasionally don't agree

[coreplayer2]

Occasionally, MyData.tgz and filetool.lst don't agree in the size of the backup.

I know when something is wrong because the cpu usage unexplainably increases and the time it takes for shutdown and bootup has increased dramatically.  when the previous shutdown and boot was normal.

My filetool list does not show anything out of the ordinary, same list of file to be included with an uncompressed size of 0.77MB and 0.55MB compressed, yet the size of the mydata.tgz file has increased to 208.68MB

When this happens (as it does occasionally), I delete the backup and make a new one, which fixes the issue (for a while at least).

How do I expand the mydata.tgz file into the /tmp directory  to see what is going on?

[curaga]

cd /tmp
mkdir test
cd test
tar xvf /path/to/mydata.tgz

[gerald_clark]

Browse it with Midnight Commander.

[coreplayer2]

Thx I didn't realize I could unpack it with tar..  and midnight commander..  Doh!!

[coreplayer2]

Ok for some reason backup had suddenly decided to include the the entire contents of the /home/tc/   yet filetool.lst indicates only some sub-directories are included within the backup. 

Meanwhile, I simply created a new backup and all is normal again..

[gerald_clark]

The default .filetool.lst contains:
opt
home

[coreplayer2]

Thanks yes I agree the default system includes home and opt, however I'm only concerned in keeping specific settings files in a frugal install.  So home and opt are not included in the filetool.lst, have not been since original install and even today not accidentally included.    I looked within the filetool.lst immediately after the error occurred and neither home or opt were listed despite the tool including home  (not opt) within the backup!! 

Though there are times after an upgrade to a new tc version I find the contents of my filetool.lst replaced by home & tc, when this happens I restore the list from a local backed up file and delete both home and opt entries.   Both the above scenario's occur often enough that I know exactly where to look to troubleshoot when the system doesn't boot as desired with personal configurations.

This system is using core 4.5.3 

[coreplayer2]

Maybe the core files have been corrupted somehow, so I've replaced core and vmlinuz   from the latest ISO download. 

[gerald_clark]

Show the output of 'showbootcodes' and the contents of .filetool.lst.
You have something configured incorrectly.