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

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

Re: [rdiff-backup-users] os error 22 detecting file system properties on


From: David Kempe
Subject: Re: [rdiff-backup-users] os error 22 detecting file system properties on cygwin
Date: Thu, 29 Jan 2004 21:15:47 +1100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Ben Escoto wrote:
Hi, hopefully we can just fix the bugs in the testing, not disable
it.  The following patch may fix two of your problems:

Hi Ben,
message from Woody one of my developers:

-------

I have corrected the patch below: :-)

It is EOPNOTSUPP, not EOPNOTSUP

Cheers,
Woody

--- fs_abilities.py.old 2004-01-27 18:12:56.000000000 -0800
+++ fs_abilities.py     2004-01-27 18:14:28.000000000 -0800
@@ -187,7 +187,7 @@
                        tmp_rp.chown(uid+1, gid+1) # just choose random
uid/gid tmp_rp.chown(0, 0)
                except (IOError, OSError), exc:
-                       if exc[0] == errno.EPERM:
+                       if exc[0] in (errno.EPERM, errno.EINVAL):
                                log.Log("Warning: ownership cannot be
changed on filesystem "
                                                "at %s" %
(self.root_rp.path,), 3)
                                self.ownership = 0
@@ -202,7 +202,8 @@
                hl_source.touch()
                try:
                        hl_dest.hardlink(hl_source.path)
-                       assert hl_source.getinode() == hl_dest.getinode()
+                       if hl_source.getinode() != hl_dest.getinode():
+                             raise IOError(errno.EOPNOTSUPP, "Hard links
don't compare")
                except (IOError, OSError), exc:
                        if exc[0] in (errno.EOPNOTSUPP, errno.EPERM):
log.Log("Warning: hard linking not supported by filesystem "

---------------

I think the wrapping broke it.
Anyway, its only a one letter fix.

After applying that patch filesystem detection didn't break anymore, so thats great. However now it runs and just stop complaining it can't find a current mirror marker. I can't make it spit out anymore errors than that - it fs detection works, then it just says destination invalid, can't find current mirror. The rdiff-backup-data dir is created and there is a log file and quoted.chars in there but no current mirror.
Is current mirror created at the begining or end of the backup?
we are testing by backing up win32 -> win32 local to local.
I think restores would work tho.
I will get back to you after testing

dave





reply via email to

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