[rdiff-backup-users] Rdiff-backup fails on cygwin

[phowell]

Hi

My previous post detailes a problem with rdiff-backup failing on the 
first attempt to backup. I have turned on full verbosity and it looks 
like some of the python libraries are not available.

Are there any issues with running 0.13.4 with python  2.3.4?
Python 2.3.4 (#1, Jun 13 2004, 11:21:03)
[GCC 3.3.1 (cygming special)] on cygwin

Output from rdiff-backup below.

Cheers

Peter Howell

$ rdiff-backup --terminal-verbosity 9 etc newtest
Mon Jul 26 10:32:47 2004  Unable to import module xattr.  EAs not 
supported on f
ilesystem at etc
Mon Jul 26 10:32:47 2004  Unable to import module posix1e from pylibacl 
package.

ACLs not supported on filesystem at etc
Mon Jul 26 10:32:47 2004  
------------------------------------------------------
-----------
Detected abilities for source (read only) file system:
 Access control lists                         Off
 Extended attributes                          Off
 Mac OS X style resource forks                Off
 Mac OS X Finder information                  Off
-----------------------------------------------------------------
Mon Jul 26 10:32:47 2004  Making directory 
newtest/rdiff-backup-data/rdiff-backu
p.tmp.0
Mon Jul 26 10:32:47 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
foo
Mon Jul 26 10:32:47 2004  Warning: ownership cannot be changed on 
filesystem at
newtest/rdiff-backup-data
Mon Jul 26 10:32:47 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
foo
Mon Jul 26 10:32:47 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
hardlinked_file1
Mon Jul 26 10:32:47 2004  Hard linking 
newtest/rdiff-backup-data/rdiff-backup.tm
p.0/hardlinked_file2 to 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_
file1
Mon Jul 26 10:32:47 2004  Directories on file system at 
newtest/rdiff-backup-dat
a/rdiff-backup.tmp.0 are not fsyncable.
Assuming it's unnecessary.
Mon Jul 26 10:32:48 2004  Unable to import module xattr.  EAs not 
supported on f
ilesystem at newtest/rdiff-backup-data/rdiff-backup.tmp.0
Mon Jul 26 10:32:48 2004  Unable to import module posix1e from pylibacl 
package.

ACLs not supported on filesystem at 
newtest/rdiff-backup-data/rdiff-backup.tmp.0

Mon Jul 26 10:32:48 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
dir_inc_check
Mon Jul 26 10:32:48 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
dir_inc_check
Mon Jul 26 10:32:48 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
regfile
Mon Jul 26 10:32:48 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
regfile
Mon Jul 26 10:32:48 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
5-_ a.
Mon Jul 26 10:32:48 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
5-_ a.
Mon Jul 26 10:32:48 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
A
Mon Jul 26 10:32:48 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
a
Mon Jul 26 10:32:48 2004  Touching 
newtest/rdiff-backup-data/rdiff-backup.tmp.0/
:
Mon Jul 26 10:32:48 2004  Deleting 
newtest/rdiff-backup-data/rdiff-backup.tmp.0
Mon Jul 26 10:32:48 2004  Removing directory 
newtest/rdiff-backup-data/rdiff-bac
kup.tmp.0
Mon Jul 26 10:32:48 2004  
------------------------------------------------------
-----------
Detected abilities for destination (read/write) file system:
 Characters needing quoting                   '^a-z0-9_ -.'
 Ownership changing                           Off
 Hard linking                                 On
 fsync() directories                          Off
 Directory inc permissions                    On
 Access control lists                         Off
 Extended attributes                          Off
 Mac OS X style resource forks                Off
 Mac OS X Finder information                  Off
-----------------------------------------------------------------
Mon Jul 26 10:32:48 2004  Fatal Error: Bad rdiff-backup-data dir on 
destination
side

The rdiff-backup data directory
newtest/rdiff-backup-data
exists, but we cannot find a valid current_mirror marker.  You can
avoid this message by removing the rdiff_backup_data directory;
however any data in it will be lost.

Probably this error was caused because the first rdiff-backup session
into a new directory failed.  If this is the case it is safe to delete
the rdiff_backup_data directory because there is no important
information in it.