Systemback

There has been critical changes in the file system during this operation.

Asked by Tom Wagner

Hello, Kendek,

I'm using an HP Laptop with Ubuntu 14.04.5 LTS installed. Previous uses of Systemback to create a restore point have been successful, but now, I have this error number 17 which happened at 100% of the process. What do I need to do to fix this? I've studied your answers for the problems relating to this, but this one is slightly different. Thanks for your help!

 The restore point creation is aborted!
 There has been critical changes in the file system during this operation.

I ran DBGLEV=3 systemback-cli -n from the console:

contents of /tmp/systemback-cli_stderr:

Systemback

Version: 1.8.402_05.16.2016_Qt5.2.1_GCC4.8.4_amd64
Compilation date and time: May 16 2016 11:16:31
Installed files: /etc/xdg/autostart/sbschedule-kde.desktop
                 /etc/xdg/autostart/sbschedule.desktop
                 /usr/bin/systemback
                 /usr/bin/systemback-cli
                 /usr/bin/systemback-sustart
                 /usr/lib/systemback/libsystemback.so
                 /usr/lib/systemback/libsystemback.so.1
                 /usr/lib/systemback/libsystemback.so.1.0
                 /usr/lib/systemback/libsystemback.so.1.0.0
                 /usr/lib/systemback/sbscheduler
                 /usr/lib/systemback/sbsustart
                 /usr/lib/systemback/sbsysupgrade
                 /usr/share/applications/systemback-kde.desktop
                 /usr/share/applications/systemback.desktop
                 /usr/share/systemback/efi-amd64.bootfiles
Operating system: Ubuntu 14.04.5 LTS
Mounted filesystems: /dev/sda1 / ext4 rw,relatime,errors=remount-ro,data=order
                     ed 0 0
System language: en_US
Translation: -

An error occurred while creating the following directory:

 /home/Systemback/.S00_2016-11-19,07.09.07/home/tom/

/home/Systemback/.S00_2016-11-19,07.09.07/home/tom/
 d rwxr-xr-x - 0 0 2049 -
/home/Systemback/.S00_2016-11-19,07.09.07/home/tom
 d rwxr-xr-x - 0 0 2049 -
/home/Systemback/.S00_2016-11-19,07.09.07/home
 d rwxr-xr-x - 0 0 2049 -
/home/Systemback/.S00_2016-11-19,07.09.07
 d rwxr-xr-x - 0 0 2049 -
/home/Systemback
 d rwxr-xr-x - 0 1000 2049 -
/home
 d rwxr-xr-x - 0 0 2049 -

Errno: 17

Question information

Language:
English Edit question
Status:
Solved
For:
Systemback Edit question
Assignee:
No assignee Edit question
Solved by:
Kendek
Solved:
Last query:
Last reply:
Revision history for this message
Best Kendek (nemh) said : 		#1

I think this is an internal error. The Systemback buffered a directory entry with empty name. So missing the name of the file:
/home/tom/<missing_file_name>
Maybe there is a directory (in the /home/tom user home dir) with special charaters or something similar.

Revision history for this message
Tom Wagner (tomwagner3) said : 		#2

I think this is an internal error. The Systemback buffered a directory entry with empty name. So missing the name of the file:
/home/tom/<missing_file_name>
Maybe there is a directory (in the /home/tom user home dir) with special charaters or something similar.

Thanks for your help, I'll take a look.
Tom

Revision history for this message
Tom Wagner (tomwagner3) said : 		#3

I think this is an internal error. The Systemback buffered a directory entry with empty name. So missing the name of the file:
/home/tom/<missing_file_name>
Maybe there is a directory (in the /home/tom user home dir) with special charaters or something similar.

Thanks for your help, I'll take a look.
Tom

I checked, don't see anything irregular...how about if I delete the systemback directory under /home? Would that make the program think this is the first backup?

Revision history for this message
Tom Wagner (tomwagner3) said : 		#4

After looking deeper in the tree, I found an irregular shape in one of the filenames. Corrected that, Systemback is working now. I appreciate the fast response and knowledge.

Revision history for this message
Tom Wagner (tomwagner3) said : 		#5

Thanks Kendek, that solved my question.

Revision history for this message
Jeff Silverman (jeffsilverm) said : 		#6

Tom,

How did you find the irregular shape?

Kendek, is there a better solution than just failing catastrophically? A lot of the files on my system are not critical, and it would be sufficient to make a note of what failed and then skip them. The idea being that the user would at least have a working system and would know what to fix "by hand".

Revision history for this message
Kendek (nemh) said : 		#7

Jeff,

the Systemback is no longer developed or maintained. But I do maintain an improved systemback.sh script, only for system backup and restoration.

https://gitlab.com/Kendek/systemback