Restore point creation aborts!

Bug #1516482 reported by ALinuxUser
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Systemback
Fix Committed
Undecided
Kendek

Bug Description

I see that this problem has been reported before. However, since the other two reports are closed, I thought I'd start a new report.

I am using Linux Mint x64 17.2 Cinnamon. I am not aware of running anything significant in the background when trying to create the restore point. I do have some restore points already, but I am loathe to delete them in case I remain unable to create restore points. Do please advise. Thank you.

Full error message:

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

You might want to note also that the above is not the best English. It should read: '. . has been aborted' and 'There have been . .'

Systemback version: 1.7.200.

Solution: change usb disk.

Revision history for this message
Kendek (nemh) wrote :

This is not full error message, please run the Systemback from terminal:

systemback-sustart

and when the problem is happened, see the error output.

Changed in systemback:
status: New → Incomplete
assignee: nobody → Kendek (nemh)
Revision history for this message
ALinuxUser (buntulongername-new) wrote : Re: [Bug 1516482] Re: Restore point creation aborts!

Dear developer

Thank you for your help and for your program. Upon following your
advice, I see the following error text in the terminal:

An error occured while creating the folowing hard link:

/home/SystemBack/.S00_2015-11-16,12.35.44/etc/teamviewer/gobal.conf

Reference file:

/home/SystemBack/S01_2015-11-09,04.37.08/etc/teamviewer/gobal.conf

I note that recently I installed a new version of TeamViewer.

Yours

Nicholas

On 16/11/2015 07:19, Kendek wrote:
> This is not full error message, please run the Systemback from terminal:
>
> systemback-sustart
>
> and when the problem is happened, see the error output.
>
> ** Changed in: systemback
> Status: New => Incomplete
>
> ** Changed in: systemback
> Assignee: (unassigned) => Kendek (nemh)
>

--
Dr Nicholas Joll

Dr Nicholas Joll

Book: /Philosophy and *The Hitchhiker's Guide to the Galaxy*/
<http://najoll.wordpress.com/hitchhiker/>

Course: Philosophy Breakfasts @ Wivenhoe Bookshop
<http://www.wivenhoebooks.com/philosophy-breakfast-2/>

Course: Philosophical Nuggets @ Red Lion Books, Colchester
<http://www.redlionbooks.co.uk/philosophical-nuggets-red-lion-books/>

Revision history for this message
Kendek (nemh) wrote :

Is this "/home/SystemBack/S01_2015-11-09,04.37.08/etc/teamviewer/gobal.conf" file exist? What the filesystem under the storage directory?
The Systemback unable to create a new hard link to this reference file. Normally this is because the file data and the - new - link (pointed to the data) are located on different filesystems. The hard linking between filesystems are not allowed (because not possible).

Revision history for this message
ALinuxUser (buntulongername-new) wrote :

Dear Kendek

Thank you for your e-mail.

That file does not exist now but it may have existed before. I think
that it cannot exist now, because I decided to delete all my old restore
points - and, having done that, SystemBack is able once again to create
restore points (although, as I have said in a different, older bug
report, I still do not really understand the SystemBack interface and,
more particularly, its two different types of check-box).

All of my file systems are EXT4 - with the exception of USB sticks (none
of which were plugged in at the time, I think), my swap partition and
possibly my CD/DVD drive, and my 'tmpfs'.

Yours

Nicholas

On 16/11/2015 16:03, Kendek wrote:
> Is this "/home/SystemBack/S01_2015-11-09,04.37.08/etc/teamviewer/gobal.conf" file exist? What the filesystem under the storage directory?
> The Systemback unable to create a new hard link to this reference file. Normally this is because the file data and the - new - link (pointed to the data) are located on different filesystems. The hard linking between filesystems are not allowed (because not possible).
>

--
Dr Nicholas Joll

Dr Nicholas Joll

Book: /Philosophy and *The Hitchhiker's Guide to the Galaxy*/
<http://najoll.wordpress.com/hitchhiker/>

Course: Philosophy Breakfasts @ Wivenhoe Bookshop
<http://www.wivenhoebooks.com/philosophy-breakfast-2/>

Course: Philosophical Nuggets @ Red Lion Books, Colchester
<http://www.redlionbooks.co.uk/philosophical-nuggets-red-lion-books/>

Revision history for this message
zustudios (zustudios504) wrote :

I did a fresh install of Ubuntu server 16.04.
Then I ran:
#add-apt-repository ppa:nemh/systemback -y
#apt update -y
#apt install xfce4 xfce4-goodies tightvncserver firefox filezilla gparted terminator synaptic systemback -y

Systemback installed but when I tried to create a restore point I get:

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

When I ran:
#systemback
I get:
QXcbConnection: Could not connect to display
Aborted (core dumped)

I get the same results when I do apt install systemback and when I install systemback manually.
I Installed on both virtualbox and proxmox with the same results.
What could I be doing wrong?

utente2015 (alfa-beta)
Changed in systemback:
status: Incomplete → Fix Committed
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.