rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rdiff-backup-users] 3 OS X issues


From: Dave Vasilevsky
Subject: [rdiff-backup-users] 3 OS X issues
Date: Tue, 08 Jun 2004 23:32:41 -0400

Hi,

Thanks to everyone who helped write rdiff-backup, the stored-metadata concept is exactly the approach I've been looking for to back up my OS X system.


To begin, I'd like to weigh in on the chars-to-quote issue. I think by default it's best to quote caps on HFS, for greatest flexibility. However, it's important to many that file-names be readable, so I think the override-chars-to-quote flag should become official for the sake of those users who are sure they won't be using their repository with a case-sensitive


Second, backing up to a sub-directory of the source directory seems to work only with relative paths (this may be a problem on other OS's too...). Strangely enough this works fine:

$ cd $HOME; rdiff-backup --exclude=$HOME/rdiff-$USER $HOME rdiff-$USER

But this yields an error:

$ rdiff-backup -v5 --exclude=$HOME/rdiff-$USER $HOME $HOME/rdiff-$USER
Traceback (most recent call last):
  File "/sw/bin/rdiff-backup", line 23, in ?
    rdiff_backup.Main.Main(sys.argv[1:])
File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 259, in Main File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 229, in take_action File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 268, in Backup File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 314, in backup_check_dirs File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 347, in backup_warn_if_infinite_regress
AttributeError: 'module' object has no attribute 'select_source'


Finally, there seems to be a bad interplay between hard links and resource forks. With ~/Hacking/bin/bitkeeper/delta as a hard link to ~/Hacking/bin/bitkeeper/admin, I see this error:

$ rdiff-backup -v7 /Users/vasi/Hacking/bin/bitkeeper test
[snip]
Processing changed file delta
Hard linking test/rdiff-backup.tmp.16 to test/admin
Copying attributes from ('delta',) to test/rdiff-backup.tmp.16
Writing resource fork to ('rdiff-backup.tmp.16',)
Traceback (most recent call last):
  File "/sw/bin/rdiff-backup", line 23, in ?
    rdiff_backup.Main.Main(sys.argv[1:])
File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 259, in Main File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 229, in take_action File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/Main.py", line 281, in Backup File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/backup.py", line 38, in Mirror File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/backup.py", line 215, in patch File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/rorpiter.py", line 279, in __call__ File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/backup.py", line 473, in fast_process File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/backup.py", line 499, in patch_to_temp File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/rpath.py", line 157, in copy_attribs File "/sw/src/root-rdiff-backup-0.13.4-1/sw/lib/python2.3/site-packages/ rdiff_backup/rpath.py", line 1143, in write_resource_fork
IOError: [Errno 13] Permission denied: 'test/rdiff-backup.tmp.16/rsrc'

It seems that rdiff-backup is trying to write a resource fork to a hard-link of a read-only file, which of course fails. In PatchITRB.patch_to_temp(), why does it do a copy_attribs() even after creating a hard link? Isn't that unnecessary?


Thanks again,
Dave Vasilevsky

Attachment: PGP.sig
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]