Can't restore fairly large backups

[Blake McBride]

I am using backintime version 1.1.2 on a current 64 bit Linux. My home directory has:

157 GB
725K files
86K directories

I have been using backintime for a few years and never had a problem with it. I am trying to restore my home directory on a new drive. It starts off fast and than hangs at some point. I waited 5 hours and it didn't move. It shows python pegging my CPU at that time. I am able to restore just fine if I take a small number of directories at a time. But attempting to highlight all the directtories at the top level of my home directory (123 of them which ultimatly containe all of the files and directores I show above).

I tried this several times with the same results. Bottom line - backintime cannot restore a large number of files at one time.

Thanks.

Blake McBride

[Germar (germar)]

Seems like this is caused by recent changes I made for enabling multi selection restore. I'll have a look on this. Thanks for reporting.

[Germar (germar)]

Could you please try out the attached patch with 'sudo patch /usr/share/backintime/common/snapshots.py < snapshots.diff'

[Blake McBride (blake-arahant)]

Yes, I will test it. Thanks!

[Jon Brase (jonathan-brase)]

Testing in my LiveCD environment, I got this:

$ sudo patch /usr/share/backintime/common/snapshots.py < Desktop/snapshots.diff
patching file /usr/share/backintime/common/snapshots.py
Hunk #1 succeeded at 428 (offset 5 lines).
Hunk #2 succeeded at 441 (offset 5 lines).
Hunk #3 FAILED at 598.
1 out of 3 hunks FAILED -- saving rejects to file /usr/share/backintime/common/snapshots.py.rej

snapshots.py.rej is attached.

[Germar (germar)]

Sorry, looks like there where to many changes since last version to simply patch it. Could you please try out current dev version from ppa:bit-team/testing instead (sudo add-apt-repository ppa:bit-team/testing && sudo apt-get update && sudo apt-get upgrade).

[Blake McBride (blake-arahant)]

I updated my system and now backintime reads version 1.1.3. I tried restoring my entire system again. Same problem. It has been running for 7 hours and is hung. CPU is pegged on python3.

[Germar (germar)]

I now made my self a test base with round about the same size to restore as yours. I hope I can reproduce it then. Thanks for testing so far...

[Germar (germar)]

I was able to reproduce it here. It was caused by the QTextEdit widget. Seems like this is getting unresponsive if there are more than ~1 million lines in there.

I now moved the restore routine into a separate thread so it doesn't freeze the GUI anymore (and vice versa) and update the log view only every 200ms. Also the log view will only show the last 100.000 lines. If you want to see more you can use the new 'Show full Log' button which will open the log in your favourite editor.

Would be great if you could run a final test from testing repository.

Regards,
Germar

PS I'll close bug #1428425 now as this is now fixed, too.

[Blake McBride (blake-arahant)]

I did a test and it worked perfectly. Thanks!!