Re: [rdiff-backup-users] os error 22 detecting file system propertieson cygwin

[David Kempe]

----- Original Message ----- 
From: "David Kempe" <address@hidden>


> I found another different error trying to do a similiar thing.

commenting out the hardlinks test and setting hardlinks = 0 now gives me
this:


C:\rdiff-backup>python2.3.exe C:\rdiff-backup\rdiff-backup --remote-schema
'plin
k -C -i sloth.PPK %s rdiff-backup --server' -v7 --print-statistics
c:\temp\drive
rs c:\temp\backup23
Remote schema option ignored - no remote file descriptions.
########## /cygdrive/c/rdiff-backup/c:\temp\drivers
/cygdrive/c/DOCUME~1/dave/LO
CALS~1/Temp
########## /cygdrive/c/rdiff-backup /cygdrive/c/DOCUME~1/dave/LOCALS~1/Temp
########## /cygdrive/c /cygdrive/c/DOCUME~1/dave/LOCALS~1/Temp
########## /cygdrive /cygdrive/c/DOCUME~1/dave/LOCALS~1/Temp
Making directory c:\temp\backup23
Making directory c:\temp\backup23/rdiff-backup-data
Unable to import module xattr.  EAs not supported on filesystem at
c:\temp\drive
rs
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at c:\temp\drivers
-----------------------------------------------------------------
Detected abilities for source (read only) file system:
  Access control lists                         Off
  Extended attributes                          Off
  Mac OS X style resource forks                Off
-----------------------------------------------------------------
Making directory c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/foo
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/foo
Directories on file system at
c:\temp\backup23/rdiff-backup-data/rdiff-backup.tm
p.0 are not fsyncable.
Assuming it's unnecessary.
Unable to import module xattr.  EAs not supported on filesystem at
c:\temp\backu
p23/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package.
ACLs not supported on filesystem at
c:\temp\backup23/rdiff-backup-data/rdiff-bac
kup.tmp.0
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/regfile
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/A
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/a
Touching c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0/:
Deleting c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0
Removing directory c:\temp\backup23/rdiff-backup-data/rdiff-backup.tmp.0
-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
  Characters needing quoting                   '^a-z0-9_ -.'
  Ownership changing                           On
  Hard linking                                 Off
  fsync() directories                          Off
  Directory inc permissions                    Off
  Access control lists                         Off
  Extended attributes                          Off
  Mac OS X style resource forks                Off
-----------------------------------------------------------------
Fatal Error: Bad rdiff-backup-data dir on destination side

The rdiff-backup data directory
c:\temp\backup23/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.


Cleaning up

Which is great, the detection seems to work nicely. shame it can't backup
for an unknown reason.
Probably due to my clumsy fiddling with fs_abilities.py

dave