Rdiff-backup v0.11.2 Release Notes

Release Date: 2003-03-01 // about 21 years ago
  • ๐Ÿ›  Fixed seg fault bug reported by a couple sparc/openbsd users. Thanks โœ… to Dave Steinberg for giving me an account on his system for testing.

    ๐Ÿ Re-enabled --windows-mode and filename quoting.

    ๐Ÿ›  Fixed selection bug: In 0.11.1, files which were included in one backup would be automatically included in the next. Now you can include/exclude files session-by-session.

    ๐Ÿ›  Fixed ownership compare bug: In 0.11.1, backups where the destination side was not root would preserve ownership information by recording it ๐Ÿ“‡ in the metadata file. However, mere ownership changes would not ๐Ÿ›  trigger creation of new increments. This has been fixed.

    โž• Added the --no-inode-compare switch. You probably don't need to use it though.

    If a special file cannot be created on the destination side, a 0 length regular file will be written instead as a placeholder. ๐Ÿ“‡ (Restores should work fine because of the metadata file.)

    Yet another error handling strategy (hopefully this is the last one for a while, because this stuff isn't very exciting, and takes a long time to write):

    All recoverable errors are classified into one of three groups:
    ListErrors, UpdateErrors, and SpecialFileErrors.  rdiff-backup's
    reaction to each error is more formally defined (see the error
    policy page, currently at
    http://rdiff-backup.stanford.edu/error_policy.html).
    
    rdiff-backup makes no attempt to recover or clean up after
    unrecoverable errors.
    
    However, it now uses fsync() to increment the destination
    directory in a reversable way.  If there is an error, the next
    backup will regress the destination directory into its state
    before the aborted backup.
    
    The above process can be done without a backup with the
    --check-destination-dir option.
    

    ๐Ÿ‘Œ Improved error logging. Instead of the old haphazard reporting method, which sometimes didn't indicate the file an error occurred on, now all recoverable errors are reported in a standard format and also written to the error_log..data file in the rdiff-backup-data directory. Thanks to Dean Gaudet and others for repeatedly bugging me about this.