Hello :-)
I get the following error using rdiff-backup 1.1.14 on cifs mounted
share.
What other information can I offer? Or what obvious error did I make? :D
rdiff-backup -v 5
--check-destination-dir /mnt/backup_local/daehne/Inetpub Using
rdiff-backup version 1.1.14 Warning: hard linking not
On 9/6/07, Mario Doering [EMAIL PROTECTED] wrote:
Hello :-)
I get the following error using rdiff-backup 1.1.14 on cifs mounted
share.
What other information can I offer? Or what obvious error did I make? :D
Your problem as far as I can tell, is trying to use a cifs mount as a
rdiff-backup
On Thu, 6 Sep 2007 12:06:46 +0200
David [EMAIL PROTECTED] wrote:
I think that your rdiff-backup is failing because it detects a failed
earlier rdiff-backup session and wants to regress to before that
failed backup. But the regress fails because rdiff-backup is unable to
set the permissions
The check command results in the same error as the
check-destination-dir.
Oops, I meant '--check-destination-dir', not '--check'. There is no
'--check' rdiff-backup option, but rdiff-backup is clever enough to
see you really wanted to use '--check-destination-dir'
rdiff-backup is started
rdiff-backup is started locally. I cannot install nfs on that machine,
but I can rsync all the stuff to another directory (ext3) and run the
check command there.
I'll report back then :)
yes.. when copied to an ext3 filesystem, the check command works.
So the rdiff error has something to
rdiff-backup is started locally.
Not sure if we're missing each other. When I said log into the remote
machine and run rdiff-backup locally, I meant locally on the other
machine.
ie:
1) ssh $REMOTEHOST
2) rdiff-backup -v 5 --check-destination-dir $DESTINATION_DIR
rdiff-backup
Mario Doering wrote:
@rdiff-backup crew:
Is this info enough for the coders to know where the problem is located?
I think it might be.
What kernel version are you running on your own system and on the server?
Andrew
--
Andrew Ferguson - [EMAIL PROTECTED]
You mean locally on the computer which contains the backup-up files
(including riff-backup-data) shared via samba?
Yes that's what I meant.
If yes, a login there is not possible. It is a terastation (=black
box) with only access via cifs.
So your backup involves pushing to the terastation
On Thu, 06 Sep 2007 09:54:20 -0400
Andrew Ferguson [EMAIL PROTECTED] wrote:
What kernel version are you running on your own system and on the
server?
I could reproduce this problem on the following kernels that mount the
cifs share:
2.6.20-xen-r1
and
2.6.14-gentoo-r4
The kernel on the
On Thu, 6 Sep 2007 16:19:03 +0200
David [EMAIL PROTECTED] wrote:
If yes, a login there is not possible. It is a terastation (=black
box) with only access via cifs.
So your backup involves pushing to the terastation
And this share is mounted on the linux system running rdiff-backup
Hi !
Does anyone know what the error below could be ?
We deleted by error a lost+found directory which was, in fact, part of
the backup structure (and not part of the filesystem). Could this be the
source of the problem ? If yes, do I have a chance to restore my backup
to a clean state ?
Many
Philippe Froidevaux wrote:
Hi !
Does anyone know what the error below could be ?
We deleted by error a lost+found directory which was, in fact, part of
the backup structure (and not part of the filesystem). Could this be the
source of the problem ? If yes, do I have a chance to restore
Matthew Flaschen wrote:
rdiff-backup follows symbolic links across filesystems with the
--exclude-other-filesystems option enabled. I expected that this option
would cause rdiff-backup to copy a symbolic link that pointed to another
FS without following it. However, rdiff-backup also follows
On 9/6/07, Matthew Flaschen [EMAIL PROTECTED] wrote:
Matthew Flaschen wrote:
rdiff-backup follows symbolic links across filesystems with the
--exclude-other-filesystems option enabled. I expected that this option
would cause rdiff-backup to copy a symbolic link that pointed to another
FS
David wrote:
If the symlink is under the backup source, then in all cases it should
always be copied as a symlink and never followed.
Mea culpa. rdiff-backup is behaving correctly and doing what I expected
originally.
The mistake I made when checking was probably (symlink_dir is a symlink
on
15 matches
Mail list logo
