SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
New issue
Author Message
Post New issue 
Well, 1.0.1 did the trick for the filetype problem, but I'm having this
problem now. I can, I think, probably fix the problem by removing the
files it thinks should be gone, but why isn't it doing that? I didn't
want to actually do that until this problem was looked at.

The recover command is same as in the previous msg:

diff-backup -v5 --print-statistics --restore-as-of 0D --force
--remote-schema '/usr/local/bin/cstream -t '$(($maxKBps * 1024))' | ssh
%s '\''rdiff-backup --server'\'' | /usr/local/bin/cstream -t
'$(($maxKBps * 1024)) . root < at > destmachine::/


Processing Changed File /home/foo/bar/file
Sending back exception [Errno 39] Directory not empty:
'/home/foo/bar/log' of type exceptions.OSError:
File "/usr/lib/python2.3/site-packages/rdiff_backup/connection.py",
line 334, in answer_request
result = apply(eval(request.function_string), argument_list)
File "/usr/lib/python2.3/site-packages/rdiff_backup/restore.py", line
317, in patch
ITR(diff.index, diff)
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line
281, in __call__
if self.finish_branches(index) is None:
File "/usr/lib/python2.3/site-packages/rdiff_backup/rorpiter.py", line
233, in finish_branches
to_be_finished.end_process()
File "/usr/lib/python2.3/site-packages/rdiff_backup/restore.py", line
680, in end_process
self.base_rp.rmdir()
File "/usr/lib/python2.3/site-packages/rdiff_backup/rpath.py", line
806, in rmdir
self.conn.os.rmdir(self.path)

Traceback (most recent call last):
File "/usr/bin/rdiff-backup", line 23, in ?
rdiff_backup.Main.Main(sys.argv[1:])
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
283, in Main
take_action(rps)
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
263, in take_action
elif action == "restore-as-of": Restore(rps[0], rps[1], 1)
File "/usr/lib/python2.3/site-packages/rdiff_backup/Main.py", line
496, in Restore
inc_rpath, dest_rp, time)
File "/usr/lib/python2.3/site-packages/rdiff_backup/restore.py", line
45, in Restore
TargetS.patch(target, diff_iter)
File "/usr/lib/python2.3/site-packages/rdiff_backup/connection.py",
line 445, in __call__
return apply(self.connection.reval, (self.name,) + args)
File "/usr/lib/python2.3/site-packages/rdiff_backup/connection.py",
line 367, in reval
if isinstance(result, Exception): raise result
OSError: [Errno 39] Directory not empty: '/home/foo/bar/log'

Post New issue 
On Wed, 19 Oct 2005, Davy Durham wrote:

The recover command is same as in the previous msg:

diff-backup -v5 --print-statistics --restore-as-of 0D --force --remote-schema
'/usr/local/bin/cstream -t '$(($maxKBps * 1024))' | ssh %s '\''rdiff-backup
--server'\'' | /usr/local/bin/cstream -t '$(($maxKBps * 1024)) .
root < at > destmachine::/

you're doing restore to the root of a machine which is live?

OSError: [Errno 39] Directory not empty: '/home/foo/bar/log'

is it possible that your dest machine has a running process which created
a file in that directory while rdiff-backup was trying to remove it?

i'm kind of skeptical of trying to restore to / on a live machine... but
maybe you've taken it down to single user and brought up the networking
interface... just curious.

-dean

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB