Hi Domonic,
It turns out that my ZFS filesystem doesn't allow renaming of symlinks *if* the
target *doesn't* exist. I've traced the problem to rpath.rename, when it's
trying to rename the tmp.N symlink to the real name, and the target doesn't
exist yet because it's later in the list.
Is it
Amending: turns out it's OS X that doesn't allow renaming of symlinks with
missing targets. I tested it on FreeBSD on my NAS, and it allows this, so OS X
has to be the culprit.
On May 22, 2013, at 3:06 PM, KP wrote:
Hi Domonic,
It turns out that my ZFS filesystem doesn't allow renaming of
I'm sorry Kevin I don't take OS X (or any Apple sauce) so I'm out of
suggestions...
Dominic
On 17/05/2013 20:09, KP wrote:
Dominic,
I added--exclude-regexp '[{}]+' after checking Spotlight to
see if any vital files would be
Hello all,
I am trying to use rdiff-backup. Client is OS X 10.7.5, using v 1.2.8. Backup
host is NAS4Free, accessed via AFP, with ZFS raidz2 storage.
The trouble occurs when backing up /. rdiff-backup stops on the following
pathname-
I neglected to include the Python error messages, see below.
My assumption about braces stemmed from advice read in other threads, that the
last pathname prior to the error spill is generally worth checking out.
No other pathnames with curly braces were found in the log file, which contains
Kevin:
Just to rule something out, try running it via a script, this way
you can get rid of the sudo on the command line. I have known cases
where sudo (under Ubuntu) causes strange behaviour with wildcards,
not involving rdiff-backup but it is worth checking.
From: rdiff-backup-users-bounces+rdiff-
backup=nedharvey@nongnu.org [mailto:rdiff-backup-users-
bounces+rdiff-backup=nedharvey@nongnu.org] On Behalf Of KP
I am trying to use rdiff-backup. Client is OS X 10.7.5, using v 1.2.8.
Backup
host is NAS4Free, accessed via AFP, with ZFS
You're trying to backup / of a mac, and the destination is Nas4Free...
Crazy idea, why not use time machine?
Time Machine occasionally throws away all backups and restarts from scratch
without asking the user. This happens when it detects corruption. I wouldn't
trust it as my only backup.
Dominic,
Ok. I put the line in a bash script (and also changed from the fs root to the
problem file's parent dir, just to get a result sooner). Same result, it looks
like.
Kevin
~/bin/backup.sh:
rdiff-backup --carbonfile \
--preserve-numerical-ids --include-special-files \
Hi Edward,
I did try, however the nas4free box doesn't show up in Time Machine's list of
time capsules / drives.
I lamely figured that happens because the NAS4Free machine is on ethernet only,
not wifi. Time Machine's system prefs panel shows only built-in hard drives,
plus 'Set Up Other
Dominic,
I added --exclude-regexp '[{}]+' after checking Spotlight to see if any vital
files would be affected (not at the moment, but future files named with {} may
be). That worked, for the narrow test case of /Applications/Adobe.
Then I modified the backup script with that exclude, to
11 matches
Mail list logo
