in symlink
self.conn.os.symlink(linktext, self.path)
OSError: [Errno 38] Function not implemented
mhh - seems that rdiff-backup stumbles on some of the filesystems incapability
of storing symlinks.
anyway - in theory rdiff-backup should be able to detect the filesystems
capabilities
dean gaudet wrote:
sounds like the bug is that rdiff-backup decides there's a metadata change
and stores an almost-empty .diff.gz file even though it's not required.
even though the metadata change is innocuous...
I think there could be a reason for the almost-empty .diff.gz file, but
it
On Sat, 18 Nov 2006, Andrew Ferguson wrote:
dean gaudet wrote:
sounds like the bug is that rdiff-backup decides there's a metadata change
and stores an almost-empty .diff.gz file even though it's not required.
even though the metadata change is innocuous...
I think there could be a
On Sat, 18 Nov 2006, dean gaudet wrote:
yep -- but we could store an actual 0-length file instead... so we're not
wasting an entire disk block on many filesystems. better to name it
.nodiff or something else so we can distinguish between an incompletely
written .diff.gz and a file with no
On Thu, 16 Nov 2006, Gordon Rowell wrote:
Has anyone looked at storing symlink metadata separately for filesystems
which don't support symlinks? In particular, when backing up to a CIFS
fileystem. This currently logs a SpecialFileError, which is not surprising.
yeah it would be desirable to
oh - it doesn#180;t ?
i never used rdiff-backup on a filesystem without symlink capability, but i
would have expected it stores symlinks in the metadata.
this is from the CHANGELOG:
Now rdiff-backup writes metadata (uid, gid, mtime, etc.) to a
compressed text file in the rdiff-backup-data
[EMAIL PROTECTED] wrote:
oh - it doesn#180;t ?
i never used rdiff-backup on a filesystem without symlink capability,
but i would have expected it stores symlinks in the metadata.
It certainly seems to:
-- excerpt from a mirror_metadata --
File SymlinkTest
Type sym
SymData a.out
Uid 0
