nssbackup-team team mailing list archive

[Jean-Peer Lorenz <722111@xxxxxxxxxxxxxxxxxx>]

Thanks for choosing sbackup and reporting this issue. I can confirm that
something's going wrong here. This is an excerpt from your log (2nd
incr. backup):

2011-02-20 11:15:06,608 - DEBUG in filecollect.collect_files(616): Creation of the complete exclude list.
2011-02-20 11:15:06,608 - DEBUG in filecollect.__cumulate_size(533): /etc/sbackup.conf: No yet included - included.
2011-02-20 11:15:06,666 - DEBUG in filecollect.__cumulate_size(529): Delta=274.177848101 - /media/Documentos/Backup Test/full.txt: 1298196581.38 > 1298196307.2
2011-02-20 11:15:06,677 - DEBUG in filecollect.__cumulate_size(533): /media/Documentos/Backup Test/INCREMENTAL.txt: No yet included - included.
2011-02-20 11:15:06,680 - DEBUG in pathparse.query_mount_uri(252): get_mount_uri: file:///media/shares/Backup/FilesTest
2011-02-20 11:15:06,680 - DEBUG in _gio_utils.query_fs_info(422): FS info - size: 157526917120 free: 79174828032
2011-02-20 11:15:06,681 - INFO in profile_handler.__collect_files(236): Summary of backup
2011-02-20 11:15:06,681 - INFO in profile_handler.__collect_files(237): Number of directories: 1.
2011-02-20 11:15:06,681 - INFO in profile_handler.__collect_files(238): Total number of files: 12.
2011-02-20 11:15:06,681 - INFO in profile_handler.__collect_files(239): Number of symlinks: 0.
2011-02-20 11:15:06,681 - INFO in profile_handler.__collect_files(240): Number of files included in snapshot: 3.
2011-02-20 11:15:06,682 - INFO in profile_handler.__collect_files(241): Number of new files (also included): 2.
2011-02-20 11:15:06,682 - INFO in profile_handler.__collect_files(242): Number of files skipped in incremental snapshot: 9.
2011-02-20 11:15:06,682 - INFO in profile_handler.__collect_files(243): Number of items forced to be excluded: 0.
2011-02-20 11:15:06,682 - INFO in profile_handler.__collect_files(244): Number of items to be excluded by config: 0.
2011-02-20 11:15:06,683 - INFO in profile_handler.__collect_files(245): Maximum free size required is '0 MiB 2 KiB 497'.

As you can see, sbackup correctly detects 2 modified files that should
get stored despite the whole 8MB TAR is storing subsequently. The
problem is related to TAR's way to detect file modifications resp. to
decide what files to store within an incremental snapshot.

In order to clarify things please comment following questions:

1. Your data (that you want to backup) are located on a NTFS partition, your backup target is a NFS share, right?
2. For test 1 + 2: no user was logged in? (i.e. no desktop session was running)?
3. Quote: "Last test: Inc backup. This time, I was logged with sudo rights user " - I don't understand exactly what you mean here. Who is logged in? Superuser (admin/root)? Was this backup manually started?
4. What happens if you start a full backup and afterwards an incr. backup manually (from config gui) without restarting your machine?
5. How to you mount your NTFS drive/NFS share?

I guess this issue is related to device numbers and how TAR handles
files on different 'devices' when creating an incr. snapshot.

Thanks for your help and valuable logs.
Best regards.
Jean-Peer

** Changed in: sbackup
       Status: New => Incomplete

** Changed in: sbackup
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/722111

Title:
  Incremental size too large in 0.11.3 and variable with user logged