bugrdiff-backup - Bugs: bug #21965, When a file's ctime has changed,...

 
 

bug #21965: When a file's ctime has changed, rdiff-backup performs a rdiff on the file's contents

Submitter:  None
Submitted:  Sun 06 Jan 2008 04:12:00 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Wont Fix
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 06 Jan 2008 05:59:31 PM UTC, comment #1: 

The mv command preserves mtimes, but changes the files content. Therefore, it is necessary to perform the rdiff if the ctime has been changed.

Assuming that a file's contents have not changed simply because the mtime has not changed is unreliable since mtime can be adjusted. Most people would agree that minimizing data loss is important in a backup program -- certainly more important than speed.


On a side note, if the backup speed is a problem for you, Beagle supports a BEAGLE_DISABLE_XATTR option. According to user reports that I have seen on the web, the speed penalty to Beagle is less than 10%.

Andrew Ferguson <owsla>
Group administrator
Sun 06 Jan 2008 04:12:00 PM UTC, original submission:  

When a file's ctime has changed, rdiff-backup performs a rdiff on the file's content, even if the file's mtime is the same as before.
This is an issue if a large amount of data should be backed up by rdiff-backup while the ctimes of the files are subject to frequent change. This happens for example when using beagle on a partition with user_xattr enabled.

rdiff-backup should only process the content of a file if the mtime has changed.


Anonymous

 

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

Attach Files:
   
   
Comment:
   

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 owsla (Posted a comment)
  •  

    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.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-01-06 owsla StatusNone Wont Fix
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code