[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rdiff-backup-users] Non recoverable error "raised of class '<type '
Re: [rdiff-backup-users] Non recoverable error "raised of class '<type 'exceptions.IOError'>':"
Sat, 5 Sep 2015 17:06:56 +0100
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
On 05/09/2015 15:52, heri wrote:
The following error concerns a file in a folder which is maintained by
rdiff-backup itself. I never changed something therein. rdiff-backup
cannot recover itself. Each run of
rdiff-backup" --include-globbing-filelist rdiff_include_f_to_r.txt
ends up with this error.
What can I do in order to fix this?
Txs in advance.
Copy from console (first three lines were written by my starter batch):
executing CMD_LINE: "C:\Program Files
rdiff_include_f_to_r.txt F:/Daten R:/Daten
Previous backup seems to have failed, regressing destination now.
[Errno 2] No such file or directory:
Exception '[Errno 2] No such file or directory:
raised of class '<type 'exceptions.IOError'>':
... File "rdiff_backup\rpath.pyc", line 1027, in touch
Traceback (most recent call last):
File "rdiff-backup", line 30, in <module>
...File "rdiff_backup\rpath.pyc", line 1027, in touch
I have not heard of this type of error before so I would tentatively
suggest that it is not the fault of rdiff-backup but some other problem
(filesystem corruption maybe?).
If this file is really missing and it is the *only* thing wrong with the
repository, you might be able to fix it just by recreating it (as it was
a nul file anyway) on the destination (this is for Windows command
prompt, with Linux or Cygwin you can use touch):
<nul (set/p z=)
Another possible clause of your difficulty, more intractable, is that
the path+name length for this 'missing' file is 272 characters - you may
be coming up against the 260 character limit for Windows paths - see
I don't of a way around this one except to say 'rdiff-backup *from*
Windows yes, but always rdiff-backup *to* Linux', which is probably not
much help in your situation. You could try physically mounting your R:
drive on a Linux system, copy the whole repo onto a Linux-based
filesystem (e.g. ext4), and then try doing a remote backup from the
Windows machine to the new repo on the Linux machine.