We have moved to a new Sailfish OS Forum. Please start new discussions there.

Backup never finished

asked 2014-05-15 00:07:44 +0300

floppy wan gravatar image

updated 2014-06-07 09:35:04 +0300

dez gravatar image

Since update I am not able to create a backup anymore. When I launch the backup the status bar moves, but nothing happens, even if I let it run more than 12 hours. I tried to backup each option (notes, messages, contacts ...) separately, but it didn't change anything.

Is there a way to do the backup with the command line and see where the application is blocking?

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

answered 2014-05-22 17:04:29 +0300

dez gravatar image

As you are using developer mode you can:

  • check journal:
$ journalctl | grep settings
  • or run jolla-settings from the command line:
$ devel-su -p
\# enter password
$ CUTES_DEBUG=1 jolla-settings
# go to backup ui and see what happens
# here you will get tracing ... 
edit flag offensive delete publish link more


I tried "CUTES_DEBUG=1 jolla-settings" and I got the following message:

[popen] git reset,--hard
Raise: {"rc":128,"stdout":"","stderr":"error: object file .git/objects/a7/3670b1efebfdbcad96c977336b913e6e10faa1 is empty\nerror: unable to find a73670b1efebfdbcad96c977336b913e6e10faa1\nerror: object file .git/objects/a7/3670b1efebfdbcad96c977336b913e6e10faa1 is empty\nfatal: loose object a73670b1efebfdbcad96c977336b913e6e10faa1 (stored in .git/objects/a7/3670b1efebfdbcad96c977336b913e6e10faa1) is corrupt\n"}

When I looked at ".git/objects/a7/", I had two files :

  • 3670b1efebfdbcad96c977336b913e6e10faa1 (0 bytes dated from 01/02/14)
  • 4c3b67284620b20ecd2b0ee06686753c09a43d (70 bytes dated from 17/03/14)

So I tried to rename 4c3b67284620b20ecd2b0ee06686753c09a43d into 4c3b67284620b20ecd2b0ee06686753c09a43d but when I tried to backup again, I got:

[popen] git reset,--hard
Raise: {"rc":128,"stdout":"","stderr":"error: sha1 mismatch

any idea?

floppy wan ( 2014-05-23 23:22:19 +0300 )edit

afaic this is some filesystem corrupion, but I can't say it for sure w/o analysing. The fact is that files are corrupted. You can try to use git fsck command

dez ( 2014-05-24 00:05:05 +0300 )edit

After renaming the two files like they were before, I ran git fsck. There is one corrupted file (empty) but in ".git/objects/0a/".

floppy wan ( 2014-05-24 00:29:14 +0300 )edit

Have you run it will --full option?

dez ( 2014-05-24 14:22:45 +0300 )edit

I never met any git db corruption in my long history of using it. Maybe for those cases something like http://git-repair.branchable.com/ should be added to the-vault

dez ( 2014-05-24 14:38:06 +0300 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2014-05-15 00:07:44 +0300

Seen: 198 times

Last updated: May 22 '14