mainstoreBackup - Support: sr #108497, Backup done but stopped at...


sr #108497: Backup done but stopped at "syncing..."

Submitter:  None
Submitted:  Fri 07 Feb 2014 12:56:16 PM UTC
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  None
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment (Rich Markup)

Fri 07 Feb 2014 08:59:04 PM UTC, comment #3: simply calls the command line program sync.

Manpage of sync says:
Force changed blocks to disk, update the super block

So, imagine someone writes a backup to an usb stick and pulls it out immediately (without umount) - things Windoze users like to do. So, calls 'sync' at the end of the backup to write all data to disk / usb stick directly. I introduced this to make things a litte bit "idiot proof" ;-) .

If you skip the sync, than the data is written after some time by the operating system. (You can manipulate this behaviour via /proc/sys/vm/dirty_writeback_centisecs.)

The option --skipSync is an undocumented feature for me for testing. So I can avoid syncing all filesystems all the time (and maybe awake disks I switched off). The only effect of not using 'sync' is having to wait the time specified in dirty_writeback_centisecs until the data is really written to disk definitely (or maybe somewhat longer if you really have a slow medium to write to).

Heinz-Josef Claes <hjclaes>
Group administrator
Fri 07 Feb 2014 02:20:33 PM UTC, comment #2: 

The option --skipSync solves the problem.
Thx for your quick response!

The backup is the first installation on this system (SuSe 11.3). There is another almost identical system (SuSe 11.3) where storeBackup is running fine. The version installed is storeBackup 3.4.3.

Just out of curiosity: What is "sync" meaning in this context? Which information is synchronized vice versa no more synchronized when using --skipSync?

Fri 07 Feb 2014 01:26:08 PM UTC, comment #1: 


not much information ...

- Can you run the backup with command line option --skipSync ?

- Did you run storeBackup for the very first time or did you use it in the past?

- Which version do you use?

- Do you have some special situation which may lead to block 'sync'?

- What happens if you call "sync" at that time additionally on the command line ( does nothing else than just calling the "sync" command.

Heinz-Josef Claes <hjclaes>
Group administrator
Fri 07 Feb 2014 12:56:16 PM UTC, original submission:  

My backup is done fine, all files are copied, but the backup log file stops at line "syncing..."

Last line in the backup-logfile:
INFO      2014.02.07 13:10:42 23247 syncing ...

The backup doesn't seem to work any longer, there are still two OS processes ( and registered, but nothing happens any more.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by hjclaes (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    No changes have been made to this item

    Back to the top

    Powered by Savane 3.11