[rdiff-backup-users] Error 1? Final moment permissions problem on target?

[Ron Leach]

List, good morning,

We're in the middle of moving our backup destination from an old 
machine (with only 2TB) to a new one with 6TB space; each of these is 
on a separate NFS share mounted under /mnt.  Our migration scheme is 
straightforward, but we hit a problem, possibly with permissions, and 
I don't understand what to do.


Migration steps:

(1) Halt the regular rdiff-backups, by commenting out the invocations 
in crontab


(2) Using the same user as the user who runs the rdiff-backups, copy 
the existing target repository onto the new destination server;

$ cd /mnt/exist-dest
$ cp -a -u -v .* -t/mnt/new-dest

(3) Execute rdiff-backup using the new machine as the destination
$ rdiff-backup --print-statistics -v3 --exclude /Source/.Trash-1000 
/Source /mnt/new-dest


(4) Check the log/report and, if ok, restore the automatic cron 
invocations, edited to backup to the new destination.



We hit a problem, though, and I don't understand what to do to fix it.

Step 2 reported an error when the cp command finished:
cp: preserving times for `/mnt/new-dest/.': Operation not permitted

The files had all 'seemed' to copy across ok, so I went ahead with 
step 3.  But step 3 failed also, at what was close to its final step 
(judging by the sequence of the timestamps on the various directories 
and files in the new destination):


Exception '[Errno 1] Operation not permitted: '/mnt/new-dest'' raised 
of class 'type 'exceptions.OSError'':


The calling tree seems to indicate a permissions cause:
[ . ]
File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line 
927, in chmod

self.conn.os.chmod(self.path, permissions  Globals.permission_mask)

called from:
[ ... ]
File /var/lib/python-support/python2.5/rdiff_backup/backup.py, line 
664, in end_process

rpath.copy_attribs(self.dir_update, self.base_rp)
File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line 
189, in copy_attribs

rpout.chmod(rpin.getperms())
File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line 
927, in chmod

self.conn.os.chmod(self.path, permissions  Globals.permission_mask)

OSError: [Errno 1] Operation not permitted: '/mnt/new-dest'


I am sure I've set something up incorrectly on the new destination, 
but the user can read and write to it so I am not sure why there might 
be a problem.  I'd also tried to make sure that the new-destination 
had the same permissions as the old-destination.  Two questions I 
would like to ask are what is the significance of the error that cp 
reported?  And what permissions 'ought' to exist on the rdiff-backup 
destination?


I'd be grateful for any comments.  I am not confident about 
permissions, in general, so even very basic remarks would be very welcome.


regards, Ron

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error 1? Final moment permissions problem on target?

[Claus-Justus Heine]

Could it be that perhaps the UID mapping is not set up correctly? Being
able to do r/w but not being able to preserve times and set permission
could indicate that somehow the NFS-Server thinks that the files are
not owned by the user issuing the command. Cam you do a chmod
manually? Or can it perhaps be that only the mount-directory
/mnt/new-dest is not owned by the backup user (the chmod error message
of rdiff-backup only mentions the mount-point)?

(BTW, perhaps it would be more efficient to run rdiff-backup through a
remote-shell instead of going through the NFS file system; however, the
setup would be slightly more complicated)

Best,

Claus


Am 15.04.14 11:00, schrieb Ron Leach:
 List, good morning,

 We're in the middle of moving our backup destination from an old machine
 (with only 2TB) to a new one with 6TB space; each of these is on a
 separate NFS share mounted under /mnt.  Our migration scheme is
 straightforward, but we hit a problem, possibly with permissions, and I
 don't understand what to do.

 Migration steps:

 (1) Halt the regular rdiff-backups, by commenting out the invocations in
 crontab

 (2) Using the same user as the user who runs the rdiff-backups, copy the
 existing target repository onto the new destination server;
 $ cd /mnt/exist-dest
 $ cp -a -u -v .* -t/mnt/new-dest

 (3) Execute rdiff-backup using the new machine as the destination
 $ rdiff-backup --print-statistics -v3 --exclude /Source/.Trash-1000
 /Source /mnt/new-dest

 (4) Check the log/report and, if ok, restore the automatic cron
 invocations, edited to backup to the new destination.


 We hit a problem, though, and I don't understand what to do to fix it.

 Step 2 reported an error when the cp command finished:
 cp: preserving times for `/mnt/new-dest/.': Operation not permitted

 The files had all 'seemed' to copy across ok, so I went ahead with step
 3.  But step 3 failed also, at what was close to its final step (judging
 by the sequence of the timestamps on the various directories and files
 in the new destination):

 Exception '[Errno 1] Operation not permitted: '/mnt/new-dest'' raised of
 class 'type 'exceptions.OSError'':

 The calling tree seems to indicate a permissions cause:
 [ . ]
 File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line
 927, in chmod
 self.conn.os.chmod(self.path, permissions  Globals.permission_mask)

 called from:
 [ ... ]
 File /var/lib/python-support/python2.5/rdiff_backup/backup.py, line
 664, in end_process
 rpath.copy_attribs(self.dir_update, self.base_rp)
 File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line
 189, in copy_attribs
 rpout.chmod(rpin.getperms())
 File /var/lib/python-support/python2.5/rdiff_backup/rpath.py, line
 927, in chmod
 self.conn.os.chmod(self.path, permissions  Globals.permission_mask)

 OSError: [Errno 1] Operation not permitted: '/mnt/new-dest'


 I am sure I've set something up incorrectly on the new destination, but
 the user can read and write to it so I am not sure why there might be a
 problem.  I'd also tried to make sure that the new-destination had the
 same permissions as the old-destination.  Two questions I would like to
 ask are what is the significance of the error that cp reported?  And
 what permissions 'ought' to exist on the rdiff-backup destination?

 I'd be grateful for any comments.  I am not confident about permissions,
 in general, so even very basic remarks would be very welcome.

 regards, Ron

 ___
 rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
 Wiki URL:
 http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


-- Claus-Justus Heine hims...@claus-justus-heine.de
http://http://www.claus-justus-heine.de/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error 1? Final moment permissions problem on target?

[Ron Leach]

On 15/04/2014 10:38, Claus-Justus Heine wrote:

Could it be that perhaps the UID mapping is not set up correctly? Being
able to do r/w but not being able to preserve times and set permission
could indicate that somehow the NFS-Server thinks that the files are
not owned by the user issuing the command. Cam you do a chmod
manually? Or can it perhaps be that only the mount-directory
/mnt/new-dest is not owned by the backup user (the chmod error message
of rdiff-backup only mentions the mount-point)?



Useful pointers, thank you.  What I find is that all the *directories* 
under /mnt/exist-dest and /mnt/new-dest have the same permissions 
(exactly as I had intended by using the -a parameter on the cp command 
to copy the existing backups to the new machine), but the mount 
points, indeed, do differ in owner and group.  Both mount points have 
permissions 40777 (shown by mc), so that any user can read and write.


In detail, the mount point of the existing backup /mnt/exist-dest has 
owner ron, group users, permissions 40777.


The mount point of the new backup /mnt/new-dest has owner root, group 
root, permissions 40777.


An obvious next step is to change the ownership of /mnt/new-dest to be 
ron, users, with permissions 40777 (and so match the exist-dest). 
Apologies for appearing over-cautious but is there any reason why I 
should not just go ahead and do that?


If so, I'll then ask rdiff-backup to check the destination which, 
hopefully, will revert this backup attempt, and try again with the 
backup.  Actually, I'll first redo the cp command to try and have it 
finish without its error, as well, we need to be able to rely on the 
integrity of the backups we already have and if there is something not 
set correctly, restores later might go awry.


Claus, thank you for the suggestion about the mount point.  (I was 
aware that NFS leads to sub-optimal performance but it was simpler to 
set up, as you mention.)


regards, Ron

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error 1? Final moment permissions problem on target?

[Claus-Justus Heine]

Am 15.04.14 13:27, schrieb Ron Leach: Useful pointers, thank you.  What
I find is that all the *directories*
 under /mnt/exist-dest and /mnt/new-dest have the same permissions
 (exactly as I had intended by using the -a parameter on the cp command
 to copy the existing backups to the new machine), but the mount points,
 indeed, do differ in owner and group.  Both mount points have
 permissions 40777 (shown by mc), so that any user can read and write.
 
 In detail, the mount point of the existing backup /mnt/exist-dest has
 owner ron, group users, permissions 40777.
 
 The mount point of the new backup /mnt/new-dest has owner root, group
 root, permissions 40777.

Personally, I would probably stick to the mount point owned by root,
would not give tmp-permissions to it but instead would create a
subdirectory for the backup below the mount-point. At least the default
ownership of the NFS-mounted volume should be owner of that directory on
the remote machine (from memory, could be wrong in this point). So maybe
one point could be to chown the matching directory of /mnt/new-dest on
the hosting server (s.t. it would be owned by the backup user). So you
probably need to change the ownership on the machine hosting the real
hard-disk (AFAIK).

Best,

Claus


-- 
Claus-Justus Heine  hims...@claus-justus-heine.de

http://http://www.claus-justus-heine.de/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error for incremental backup on Mac

[Sai kee Wong]

Got following error, I am not familiar with troubleshooting with
rdiff-backup, can anyone suggest some way for me to troubleshoot ?

Thanks in advance.

SK

Previous backup seems to have failed, regressing destination now.
Exception 'Bad index order: ('long_filename_data', '1') = ('ctse', 'Library', 
'Mail', 'V2', 'imap-cathypy...@gmail.com@imap.gmail.com', '[Gmail].mbox', 'All 
Mail.mbox', '05D20631-00E8-46C9-A4DC-3AC8C76717F5', 'Data', '2', '6', 
'Attachments', '62150')' raised of class 'type 'exceptions.AssertionError'':
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 306, in 
error_check_Main
   try: Main(arglist)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 326, in 
Main
   take_action(rps)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 282, in 
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 339, in 
Backup
   backup_final_init(rpout)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 504, in 
backup_final_init
   checkdest_if_necessary(rpout)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 938, in 
checkdest_if_necessary
   dest_rp.conn.regress.Regress(dest_rp)
 File /Library/Python/2.7/site-packages/rdiff_backup/regress.py, line 71, in 
Regress
   for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
 File /Library/Python/2.7/site-packages/rdiff_backup/rorpiter.py, line 275, 
in __call__
   assert 0, Bad index order: %s = %s % (self.index, index)

Traceback (most recent call last):
 File /usr/local/bin/rdiff-backup, line 30, in module
   rdiff_backup.Main.error_check_Main(sys.argv[1:])
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 306, in 
error_check_Main
   try: Main(arglist)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 326, in 
Main
   take_action(rps)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 282, in 
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 339, in 
Backup
   backup_final_init(rpout)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 504, in 
backup_final_init
   checkdest_if_necessary(rpout)
 File /Library/Python/2.7/site-packages/rdiff_backup/Main.py, line 938, in 
checkdest_if_necessary
   dest_rp.conn.regress.Regress(dest_rp)
 File /Library/Python/2.7/site-packages/rdiff_backup/regress.py, line 71, in 
Regress
   for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
 File /Library/Python/2.7/site-packages/rdiff_backup/rorpiter.py, line 275, 
in __call__
   assert 0, Bad index order: %s = %s % (self.index, index)
AssertionError: Bad index order: ('long_filename_data', '1') = ('ctse', 
'Library', 'Mail', 'V2', 'imap-cathypy...@gmail.com@imap.gmail.com', 
'[Gmail].mbox', 'All Mail.mbox', '05D20631-00E8-46C9-A4DC-3AC8C76717F5', 
'Data', '2', '6', 'Attachments', '62150')___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error handling and mailing list

[Iván Pulido]

Hey, I'm a new rdiff-backup user having some question on how to handle
errors.

First I'd like to point out that the link to the mailing list in
http://rdiff-backup.nongnu.org/savannah.html#mailing_list
is broken.

Now, the real question is that, I'm using inside a bash script for
backup a command like the following:

rdiff-backup -v3 --force --remove-older-than 3W $i

where the iterator i stands for some directories. My doubt is how to
detect when there is an error in rdiff-backup
while executing this script. I need that so I can use that to actually
know the backup was succesfull or not.

Thanks for your attention and I hope this isn't a too noobish question.

Greetings.

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Joe Steele]

In all likelihood, your problem is caused by hardlinked files in 
your backup.  The --verify and --compare-hash directives in 
version 1.2.8 have problems with such files.


You might take a look at bug report #26848:
https://savannah.nongnu.org/bugs/?26848

I have just now updated the report with a couple patches that 
might help.


--Joe

On 8/7/2010 11:49 AM, Robinson, Eric wrote:

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive.

First I get tons of these messages...

Warning: Metadata file has no digest forfile, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found.  Directory matches archive data.

So if it can't compare, why would it say the directory matches?

And what is the problem with the hash in the first place?

--
Eric Robinson


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THENNochanges found. Directory matches. What?

[Steven Willoughby]

On 08/11/2010 08:03 PM, Robinson, Eric wrote:

 I've never tried using --compare-hash.
 There has been a lot of talk in the past about how to
 verify backups and really for me the only full proof solution
 is to restore somewhere and compare (diff) against original.

Unfortunately, I am talking about directories with up to 2 million files
each. I can't really afford (in terms of time or storage) to copy the
data from the backup server to the source servers and compare it that
way. Is there no way to do a good in-place comparison?


The rdiff-backup comparison should work if you're using a recent 
rdiff-backup on both ends.  (As mentioned in my last email.) If you only 
care about comparing with the most recent backup then you could probably 
do something like:


rsync -azv --del --dry-run --exclude=rdiff-backup-data/ $source/ $backup/

This should print out a list of all files that have changed.  To do a 
full comparison you'll want to add -I.


Steven

P.S.  In the past I have also done this with something like the following:

find $source -type f -exec md5sum {} \; | sort -k 2  /tmp/source
find $dest -type f -exec md5sum {} \; | sort -k 2  /tmp/dest
diff /tmp/source /tmp/dest

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

RE: [rdiff-backup-users] Error Unable to compare BUT THENNochanges found. Directory matches. What?

[Robinson, Eric]

 The rdiff-backup comparison should work if you're 
 using a recent rdiff-backup on both ends.  

You mean the rdiff-backup version? It's 1.2.8 on both servers. But does
it to an in-place comparison? If I understand the man page correctly, it
first copies the data from the dest to the source and then compares it
there?


 If you only care about comparing with the most 
 recent backup then you could probably do something like:
 rsync -azv --del --dry-run --exclude=rdiff-backup-data/ 
 $source/ $backup/

I definitely care about more than just the most recent backup. I need to
be able to restore from prevous days, weeks, and months, which was the
whole point of using rdiff-backup in the first place. But I can
understand using the most recent backup as a benchmark for testing the
backup quality.

 P.S.  In the past I have also done this with 
 something like the following:

 find $source -type f -exec md5sum {} \; | sort -k 2  
 /tmp/source find $dest -type f -exec md5sum {} \; | 
 sort -k 2  /tmp/dest diff /tmp/source /tmp/dest

That could work, too. Thanks for the suggestion.

I'd still rather just use something built into rdiff-backup if possible.



Disclaimer - August 12, 2010 
This email and any files transmitted with it are confidential and intended 
solely for Steven Willoughby,rdiff-backup-us...@nongnu.org. If you are not the 
named addressee you should not disseminate, distribute, copy or alter this 
email. Any views or opinions presented in this email are solely those of the 
author and might not represent those of Physicians' Managed Care or Physician 
Select Management. Warning: Although Physicians' Managed Care or Physician 
Select Management has taken reasonable precautions to ensure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THENNochanges found. Directory matches. What?

[Steven Willoughby]

On 08/12/2010 03:55 PM, Robinson, Eric wrote:

You mean the rdiff-backup version? It's 1.2.8 on both servers. But does
it to an in-place comparison? If I understand the man page correctly, it
first copies the data from the dest to the source and then compares it
there?


I'm also running 1.2.8 on my hosts, I'm not sure why you are getting 
warnings with --compare-hash.  In any case, I think you misunderstood 
the man page (if you're talking about what it says for --compare-hash). 
 It will re-read all of the data on the source side in order to compute 
a hash and then compare that hash with what is stored in the backup 
metadata.  I haven't seen the code in question or ever used this option 
before yesterday so I'm not 100% sure that the data won't be transferred 
over the network, but it shouldn't be.




I definitely care about more than just the most recent backup. I need to
be able to restore from prevous days, weeks, and months, which was the
whole point of using rdiff-backup in the first place. But I can
understand using the most recent backup as a benchmark for testing the
backup quality.


If you're testing backup quality then you should use the 
--verify-at-time option instead of the --compare option.  I have been 
using it in production (debian stable, rdiff-backup 1.2.5) for a long 
time.  I think the intention of the --compare option is to see what 
files have changed on the source, not to verify old backups.


Steven

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

RE: [rdiff-backup-users] Error Unable to compare BUT THENNochanges found. Directory matches. What?

[Robinson, Eric]

 I think you misunderstood the man page (if you're 
 talking about what it says for --compare-hash). 

I was talking about using compare-full as an alternative to
compare-hash. I believe the man page states that compare-full brings the
whole file over from the dest to the source and compares it there, which
is a very costly operation.

 If you're testing backup quality then you should use 
 the --verify-at-time option instead

Will check it out!

--
Eric Robinson




Disclaimer - August 12, 2010 
This email and any files transmitted with it are confidential and intended 
solely for Steven Willoughby,rdiff-backup-us...@nongnu.org. If you are not the 
named addressee you should not disseminate, distribute, copy or alter this 
email. Any views or opinions presented in this email are solely those of the 
author and might not represent those of Physicians' Managed Care or Physician 
Select Management. Warning: Although Physicians' Managed Care or Physician 
Select Management has taken reasonable precautions to ensure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Steven Willoughby]

On 08/10/2010 04:16 PM, Robinson, Eric wrote:


It's quiet.

Yeah, too quiet. Gives me the willies.

Me, too.

--
Eric Robinson



-Original Message-
From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
On Behalf Of Robinson, Eric
Sent: Saturday, August 07, 2010 8:50 AM
To: rdiff-backup-users@nongnu.org
Subject: [rdiff-backup-users] Error Unable to compare BUT THEN No
changesfound. Directory matches. What?

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive.

First I get tons of these messages...

Warning: Metadata file has no digest forfile, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found.  Directory matches archive data.

So if it can't compare, why would it say the directory matches?



I have been running rdiff-backup for a long time with the --verify 
option which does something similar with no issues.  The --compare-hash 
option also seems to be working perfectly for me.  Adding -v6 to your 
command might be enlightening.



And what is the problem with the hash in the first place?



The hash should be stored in 
$backup_dir/rdiff-backup-data/mirror_metadata.$date.  Try looking at the 
mirror_metadata snapshot previous to the current one (you should be able 
to open it with zless or zcat).  IIRC older versions of rdiff-backup 
(like 1.0) didn't store this hash, so perhaps it is missing.  If that 
was the case then that would explain the warnings and the No changes 
found. is probably a bug since it didn't find any files that didn't 
match (since all of them were skipped.)


It might work to use the --compare-full option if you haven't been 
storing hashes.


Steven

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Marian 'VooDooMan' Meravy]

EHLO

Greetings,

devels: rdiff-backup stores data by using industry standard gzip. But
bz2 has better compression. Or even usage of 7zip, which is not
industry standard but everyone is using it, so it will become industry
standard sooner or later, and it has more aggressive compression than
all other zip algorithms (it has even multi-thread support, so SMP
kernels and multi-core systems can use advantage of it). PS: 7zip AFAIK
has library installed besides command-line tool `mc` - midnight
commander is using it) - I'm not sure about .so library, but I'm really
sure that bz2 package _HAS_ library, I mean .so on unices, on windows,
there should be .dll as well).

would it be possible to implement bz2, or even 7zip ?

on windows installation (e.g. cygwin) can place dependency for
compression libraries...

Best,
VooDooMan
.

On 11. 8. 2010 20:00, Steven Willoughby wrote:
 On 08/10/2010 04:16 PM, Robinson, Eric wrote:

 It's quiet.

 Yeah, too quiet. Gives me the willies.

 Me, too.

 -- 
 Eric Robinson



 -Original Message-
 From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
 [mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
 On Behalf Of Robinson, Eric
 Sent: Saturday, August 07, 2010 8:50 AM
 To: rdiff-backup-users@nongnu.org
 Subject: [rdiff-backup-users] Error Unable to compare BUT THEN No
 changesfound. Directory matches. What?

 I've been using rdiff-backup for a while, but today was the first time I
 tried using the --compare-hash directive.

 First I get tons of these messages...

 Warning: Metadata file has no digest forfile, unable to
 compare.

 That's scary enough by itself. But then at the end it says...

 No changes found.  Directory matches archive data.

 So if it can't compare, why would it say the directory matches?

 
 I have been running rdiff-backup for a long time with the --verify
 option which does something similar with no issues.  The --compare-hash
 option also seems to be working perfectly for me.  Adding -v6 to your
 command might be enlightening.
 
 And what is the problem with the hash in the first place?

 
 The hash should be stored in
 $backup_dir/rdiff-backup-data/mirror_metadata.$date.  Try looking at the
 mirror_metadata snapshot previous to the current one (you should be able
 to open it with zless or zcat).  IIRC older versions of rdiff-backup
 (like 1.0) didn't store this hash, so perhaps it is missing.  If that
 was the case then that would explain the warnings and the No changes
 found. is probably a bug since it didn't find any files that didn't
 match (since all of them were skipped.)
 
 It might work to use the --compare-full option if you haven't been
 storing hashes.
 
 Steven
 
 ___
 rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
 Wiki URL:
 http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
 


0x7AEE5167.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THENNochanges found. Directory matches. What?

[Robinson, Eric]

 I've never tried using --compare-hash.

 There has been a lot of talk in the past about how to 
 verify backups and really for me the only full proof solution 
 is to restore somewhere and compare (diff) against original.

Unfortunately, I am talking about directories with up to 2 million files
each. I can't really afford (in terms of time or storage) to copy the
data from the backup server to the source servers and compare it that
way. Is there no way to do a good in-place comparison? 
 
--
Eric Robinson

 


Disclaimer - August 11, 2010 
This email and any files transmitted with it are confidential and intended 
solely for Gavin,rdiff-backup-us...@nongnu.org. If you are not the named 
addressee you should not disseminate, distribute, copy or alter this email. Any 
views or opinions presented in this email are solely those of the author and 
might not represent those of Physicians' Managed Care or Physician Select 
Management. Warning: Although Physicians' Managed Care or Physician Select 
Management has taken reasonable precautions to ensure no viruses are present in 
this email, the company cannot accept responsibility for any loss or damage 
arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

RE: [rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Robinson, Eric]

 
It's quiet.

Yeah, too quiet. Gives me the willies.

Me, too.

--
Eric Robinson



-Original Message-
From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
On Behalf Of Robinson, Eric
Sent: Saturday, August 07, 2010 8:50 AM
To: rdiff-backup-users@nongnu.org
Subject: [rdiff-backup-users] Error Unable to compare BUT THEN No
changesfound. Directory matches. What?

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive. 

First I get tons of these messages...

Warning: Metadata file has no digest for file, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found.  Directory matches archive data.

So if it can't compare, why would it say the directory matches? 

And what is the problem with the hash in the first place? 

--
Eric Robinson


Disclaimer - August 7, 2010
This email and any files transmitted with it are confidential and
intended solely for rdiff-backup-us...@nongnu.org. If you are not the
named addressee you should not disseminate, distribute, copy or alter
this email. Any views or opinions presented in this email are solely
those of the author and might not represent those of Physicians' Managed
Care or Physician Select Management. Warning: Although Physicians'
Managed Care or Physician Select Management has taken reasonable
precautions to ensure no viruses are present in this email, the company
cannot accept responsibility for any loss or damage arising from the use
of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Gavin]

Lol, hi Eric.

Looks like no-one has any ideas and I've never tried using --compare-hash.
Also now I'm too scared to cause if I see errors they will worry me and
I will want to fix them when there may be not much wrong lol.

There has been a lot of talk in the past about how to verify backups and
really
for me the only full proof solution is to restore somewhere and compare
(diff) against original.

Cheers
Gavin

Robinson, Eric wrote:
  
 It's quiet.

 Yeah, too quiet. Gives me the willies.

 Me, too.

 --
 Eric Robinson



 -Original Message-
 From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
 [mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
 On Behalf Of Robinson, Eric
 Sent: Saturday, August 07, 2010 8:50 AM
 To: rdiff-backup-users@nongnu.org
 Subject: [rdiff-backup-users] Error Unable to compare BUT THEN No
 changesfound. Directory matches. What?

 I've been using rdiff-backup for a while, but today was the first time I
 tried using the --compare-hash directive. 

 First I get tons of these messages...

   Warning: Metadata file has no digest for file, unable to
 compare.

 That's scary enough by itself. But then at the end it says...

   No changes found.  Directory matches archive data.

 So if it can't compare, why would it say the directory matches? 

 And what is the problem with the hash in the first place? 

 --
 Eric Robinson


 Disclaimer - August 7, 2010
 This email and any files transmitted with it are confidential and
 intended solely for rdiff-backup-us...@nongnu.org. If you are not the
 named addressee you should not disseminate, distribute, copy or alter
 this email. Any views or opinions presented in this email are solely
 those of the author and might not represent those of Physicians' Managed
 Care or Physician Select Management. Warning: Although Physicians'
 Managed Care or Physician Select Management has taken reasonable
 precautions to ensure no viruses are present in this email, the company
 cannot accept responsibility for any loss or damage arising from the use
 of this email or attachments. 
 This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

 ___
 rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
 Wiki URL:
 http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

 ___
 rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
 Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

   

-- 
www.gnumims.org http://www.gnumims.org
www.kromhouts.net http://www.kromhouts.net
Everything in moderation, including moderation itself.
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error Unable to compare BUT THEN No changes found. Directory matches. What?

[Robinson, Eric]

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive. 

First I get tons of these messages...

Warning: Metadata file has no digest for file, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found.  Directory matches archive data.

So if it can't compare, why would it say the directory matches? 

And what is the problem with the hash in the first place? 

--
Eric Robinson


Disclaimer - August 7, 2010 
This email and any files transmitted with it are confidential and intended 
solely for rdiff-backup-us...@nongnu.org. If you are not the named addressee 
you should not disseminate, distribute, copy or alter this email. Any views or 
opinions presented in this email are solely those of the author and might not 
represent those of Physicians' Managed Care or Physician Select Management. 
Warning: Although Physicians' Managed Care or Physician Select Management has 
taken reasonable precautions to ensure no viruses are present in this email, 
the company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error trying to forget a backed-up file

[Steve White]

Hi again,

To follow up on this:

The backup was unfortunately lost, as has always happened before when
these problems occurred.

However with Andreas' help, we got more information as to what happened.

The original problem was triggered by a monster file that was too big to
copy to the backup.  However it was also too big to fit in the temporary
directories -- it isn't clear that this was involved in the original problem
howeever.

I removed the monster file and the corresponding increments files, and
attempted another backup.  It said something about regressing, then said
it was out of space, althogh there was plenty of space on the source
and backup partitions.  By this point, the backup was trashed, I think.

However, we determined that this out-of-space problem was due to 
insufficient space in the tempdir partitions on both source and 
destination (by default, it uses /tmp).  When I rdiff-backup to bigger
partitions, it proceeded; but it proceeded to replace many of the
backed-up files with empty files.

This seems to be a data-losing bug.

Another strange thing is; after deleting the files as described, 
rdiff-backup was still looking for them.  

* Question: where else does rdiff-backup keep info about backed-up files,
besides the increments files?

Below is part of of the output after pointing to bigger tempdirs. 
The monster file was in 'cache-dir', which was deleted.
The substituting empty file errors indicate data loss.


Previous backup seems to have failed, regressing destination now.
Error reading /work3/backup/mintaka/opt/jsdk-xx/apache-tomcat-5.5.12/work/Catali
na/localhost/lenya/cocoon-files/cache-dir/cocoon-ehcache-1.data, substituting em
pty file.
Error reading /work3/backup/mintaka/opt/jsdk-xx/apache-tomcat-5.5.12/work/Catali
na/localhost/lenya/cocoon-files/cache-dir/cocoon-ehcache-1.index, substituting e
mpty file.
Error reading /work3/backup/mintaka/opt/jsdk-xx/apache-tomcat-5.5.12/work/Catali
na/localhost/webdav/SESSIONS.ser, substituting empty file.
Error reading /work3/backup/mintaka/opt/jsdk-xx/vomrs-tomcat/apache-tomcat-5.5.1
2/conf/tomcat-users.xml, substituting empty file.

...

Error reading /work3/backup/mintaka/work4/mnt/logs/vomrs_astrogrid-d.log.1, subs
tituting empty file.
Error reading /work3/backup/mintaka/work4/mnt/logs/vomrs_astrogrid-d.log.2, subs
tituting empty file.
Warning: Could not restore file work4/mnt/work/Catalina/localhost/lenya/cocoon-f
iles/cache-dir/cocoon-ehcache-1.data!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
Warning: Could not restore file work4/mnt/work/Catalina/localhost/lenya/cocoon-f
iles/cache-dir/cocoon-ehcache-1.index!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
Warning: Could not restore file work4/mnt/work/Catalina/localhost/lenya/cocoon-f
iles/cache-dir/cocoon-ehcache-2.data!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
Warning: Could not restore file work4/mnt/work/Catalina/localhost/lenya/cocoon-f
iles/cache-dir/cocoon-ehcache-2.index!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup


Cheers!

On  1.03.10, Steve White wrote:
 Hi,
 
 I'm again having a problem with the old issue of having rdiff-backup
 forget a file that was accidentally backed up.
 
 I double checked the FAQ and Wiki, but there really isn't a solution yet.
 It would be very good to have an official means of solving these problems.
 
 There was a discussion last month
   Techniques for trimming the sizes of backups
 The suggested remedy was
   remove the undesired files
   remove the corresponding increments files
 I tried this and it failed, as below.
 
 What happened was: some process had run wild resulting in a relatively 
 small cache file growing to many gigs.  On the next backup, rdiff-backup
 tried to back it up and ran out of space.
 
 So I 

[rdiff-backup-users] Error trying to forget a backed-up file

[Steve White]

Hi,

I'm again having a problem with the old issue of having rdiff-backup
forget a file that was accidentally backed up.

I double checked the FAQ and Wiki, but there really isn't a solution yet.
It would be very good to have an official means of solving these problems.

There was a discussion last month
Techniques for trimming the sizes of backups
The suggested remedy was
remove the undesired files
remove the corresponding increments files
I tried this and it failed, as below.

What happened was: some process had run wild resulting in a relatively 
small cache file growing to many gigs.  On the next backup, rdiff-backup
tried to back it up and ran out of space.

So I removed the files involved as suggested, and told rdiff-backup to
exclude the cache directory.  There is now plenty of free space on both
target and destination server.  But rdiff-backup still fails, saying there
is no space left...

--
Previous backup seems to have failed, regressing destination now.
Exception '[Errno 28] No space left on device' raised of class 
'exceptions.IOError':
  File /usr/lib64/python2.4/site-packages/rdiff_backup/robust.py, line 32, in 
check_common_error
try: return function(*args)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/restore.py, line 468, 
in get_fp
Rdiff.write_patched_fp(current_fp, delta_fp, new_fp)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Rdiff.py, line 73, in 
write_patched_fp
rpath.copyfileobj(librsync.PatchedFile(basis_fp, delta_fp), out_fp)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 64, in 
copyfileobj
outputfp.write(inbuf)

Exception '[Errno 28] No space left on device' raised of class 
'exceptions.IOError':
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 304, in 
error_check_Main
try: Main(arglist)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 324, in 
Main
take_action(rps)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 280, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup_final_init(rpout)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 501, in 
backup_final_init
checkdest_if_necessary(rpout)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 920, in 
checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/connection.py, line 
450, in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/connection.py, line 
370, in reval
if isinstance(result, Exception): raise result

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 30, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 304, in 
error_check_Main
try: Main(arglist)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 324, in 
Main
take_action(rps)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 280, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup_final_init(rpout)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 501, in 
backup_final_init
checkdest_if_necessary(rpout)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line 920, in 
checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/connection.py, line 
450, in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /usr/lib64/python2.3/site-packages/rdiff_backup/connection.py, line 
370, in reval
if isinstance(result, Exception): raise result
IOError: [Errno 28] No space left on device
--

Cheers!

-- 
| -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
| Steve White +49(331)7499-202
| e-Science / AstroGrid-D   Zi. 35  Bg. 20
| -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -
| Astrophysikalisches Institut Potsdam (AIP)
| An der Sternwarte 16, D-14482 Potsdam
|
| Vorstand: Prof. Dr. Matthias Steinmetz, Peter A. Stolz
|
| Stiftung privaten Rechts, Stiftungsverzeichnis Brandenburg: III/7-71-026
| -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error: command gcc failed with exit status 1

[koolnyze]

Hello,

The package names required are python-devel and librsync-devel

+--
|This was sent by kooln...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error

[Piotr Karbowski]

On Tue, Sep 22, 2009 at 5:55 PM, prateekmoturi
rdiff-backup-fo...@backupcentral.com wrote:

 Hi i am getting the following error messages when i am trying to backup.
 I am using the rdiff-backup 1.2.8.
 Can anyone please help me to find the solution for the following error...

 IOError: CRC check failed


Look for me like problem with files, broken hdd? Corruped filesystem?
Something is definitly wrong.


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error

[Dominic Raferd]

prateekmoturi wrote:

Hi i am getting the following error messages when i am trying to backup.
I am using the rdiff-backup 1.2.8.
Can anyone please help me to find the solution for the following error...


Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 30, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 304, in 
error_check_Main
try: Main(arglist)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 324, in 
Main
take_action(rps)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 280, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup_final_init(rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 501, in 
backup_final_init
checkdest_if_necessary(rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 920, in 
checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /usr/lib/python2.4/site-packages/rdiff_backup/regress.py, line 71, in 
Regress
for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
  File /usr/lib/python2.4/site-packages/rdiff_backup/regress.py, line 197, in 
iterate_meta_rfs
for raw_rf, metadata_rorp in collated:
  File /usr/lib/python2.4/site-packages/rdiff_backup/rorpiter.py, line 100, 
in Collate2Iters
try: relem2 = riter2.next()
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 274, 
in iterate
for record in self.iterate_records():
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 283, 
in iterate_records
next_pos = self.get_next_pos()
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 266, 
in get_next_pos
newbuf = self.fileobj.read(self.blocksize)
  File /usr/lib/python2.4/gzip.py, line 225, in read
self._read(readsize)
  File /usr/lib/python2.4/gzip.py, line 273, in _read
self._read_eof()
  File /usr/lib/python2.4/gzip.py, line 309, in _read_eof
raise IOError, CRC check failed
IOError: CRC check failed
  
This is what Andrew Ferguson (maintainer of rdiff-backup) wrote in 
response to a similar problem a couple of years ago:


Given this error, and especially since one client is failing and three
are working, I would be suspicious of the failing client's hardware
(probably RAM or hard disk). Are all of your clients backing up to one
server? What is the setup here?

CRC is the Cyclic Redundancy Check and is a way of checking the
integrity of a data stream.

Were there any other messages logged from rdiff-backup? Perhaps in the
rdiff-backup-data/error_log files?

And here is what someone else wrote about this error:

This problem has come up many times on the mailing list, and so far there 
is not a good fix for it... usually it appears when one of the .gz files was 
incomplete.  Try this:


find rdiff-backup-data/ -name '*.gz | while read a; do
   echo -n $a:
   gzip --test $a
done

This will tell you which files are bad.  In our case, we had a problem 
with the mirror_metadata files.  Search the archive for specifics, but 
basically I copied a good mirror_metadata over the bad mirror_metadata and 
crossed my fingers.  It worked for us, though I do not know the 
implications here.  After doing this surgery, you might try a restore of 
the past few backup dates and make sure it is successful.  Worst case, you 
rm-rf rdiff-backup-data, though you will loose your increments.


HTH, Dominic



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error

[prateekmoturi]

Hi i am getting the following error messages when i am trying to backup.
I am using the rdiff-backup 1.2.8.
Can anyone please help me to find the solution for the following error...


Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 30, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 304, in 
error_check_Main
try: Main(arglist)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 324, in 
Main
take_action(rps)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 280, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup_final_init(rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 501, in 
backup_final_init
checkdest_if_necessary(rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 920, in 
checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /usr/lib/python2.4/site-packages/rdiff_backup/regress.py, line 71, in 
Regress
for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
  File /usr/lib/python2.4/site-packages/rdiff_backup/regress.py, line 197, in 
iterate_meta_rfs
for raw_rf, metadata_rorp in collated:
  File /usr/lib/python2.4/site-packages/rdiff_backup/rorpiter.py, line 100, 
in Collate2Iters
try: relem2 = riter2.next()
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 274, 
in iterate
for record in self.iterate_records():
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 283, 
in iterate_records
next_pos = self.get_next_pos()
  File /usr/lib/python2.4/site-packages/rdiff_backup/metadata.py, line 266, 
in get_next_pos
newbuf = self.fileobj.read(self.blocksize)
  File /usr/lib/python2.4/gzip.py, line 225, in read
self._read(readsize)
  File /usr/lib/python2.4/gzip.py, line 273, in _read
self._read_eof()
  File /usr/lib/python2.4/gzip.py, line 309, in _read_eof
raise IOError, CRC check failed
IOError: CRC check failed


Thanks in advance

+--
|This was sent by prateekmot...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error 13

[listserv . traffic]

I'm getting this error again. Last time I got it, I started a new
repository.

But it's back...

Here's a -v 6 listing around the error.

---
Processing changed file Shared-docs/Abc/Jiff's Document Info.1234.QBW.nd
Regular copying ('Shared-docs', 'Abc', Jiff's Document Info.1234.QBW.nd) to 
e:/sepco-data/Shared-docs/Abc/rdiff-backup.tmp.10744
Incrementing mirror file e:/sepco-data/Shared-docs/Abc/Jiff's Document 
Info.1234.QBW.nd
Exception '[Errno 13] Permission denied: 'c:/Sepco-Data/Shared-docs/Abc/Speedy 
Spooner  Forker Service.GWC..QBW'' raised of class 'type 
'exceptions.IOError'':
  File rdiff_backup\robust.pyc, line 32, in check_common_error
  File rdiff_backup\Rdiff.pyc, line 61, in get_delta_sigrp_hash
  File rdiff_backup\rpath.pyc, line 1174, in open

Processing changed file Shared-docs/Abc/Speedy Spooner  Forker Service.GWC..QBW
Regular copying ('Shared-docs', 'Abc', 'Speedy Spooner  Forker 
Service.GWC..QBW') to e:/sepco-data/Shared-docs/Abc/rdiff-backup.tmp.10745
Incrementing mirror file e:/sepco-data/Shared-docs/Abc/Speedy Spooner  Forker 
Service.GWC..QBW
Regular copying ('Shared-docs', 'Abc', 'Speedy Spooner  Forker 
Service.GWC..QBW') to 
e:/sepco-data/rdiff-backup-data/increments/Shared-docs/Abc/Speedy Spooner  
Forker Service.GWC..QBW.2009-05-21T20-00-02-07-00.snapshot.gz
Backup pass finished at: 2009-05-29-Fri-20.18.28

---
What's odd is that it claims it finished the backup pass, but
rdiff-backup exits with a 255 code.

It also regresses the next backup before starting, so clearly it
doesn't think it ended correctly not-withstanding the log.

---
Help!

Details:
RDiff-Backup 1.3.3 on Windows, using windows native binary.
Source and Dest are local sata disks.
NTFS partitions on both systems.
TIA!
-Greg



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error 13

[Marcel (Felix) Giannelia]

My guess would be that the file is open, but Windows has several 
different ways of locking a file open and then being nasty to other 
programs trying to use it --


- The way the registry .DAT file is kept open while a user is logged in 
-- makes the file totally inaccessible to anything, error message is a 
generic file access error / read error.


- The way Word documents are kept open by later versions of Word (2003 
and 2007), and PDF documents by later versions of acrobat reader -- file 
access may or may not be totally denied to everything else, and you get 
an error that says this file is being used by the following program: 
name of program.


Maybe QuickBooks recently changed from method 1 to method 2 of locking 
files open and rdiff-backup doesn't like it -- try locking a Word 
document open that way and running rdiff-backup on it; see if it 
complains. Also try rdiff-backup'ing your registry and see if the error 
is different.


~Felix.

listserv.traf...@sloop.net wrote:

I'm getting this error again. Last time I got it, I started a new
repository.

But it's back...

Here's a -v 6 listing around the error.

---
Processing changed file Shared-docs/Abc/Jiff's Document Info.1234.QBW.nd
Regular copying ('Shared-docs', 'Abc', Jiff's Document Info.1234.QBW.nd) to 
e:/sepco-data/Shared-docs/Abc/rdiff-backup.tmp.10744
Incrementing mirror file e:/sepco-data/Shared-docs/Abc/Jiff's Document 
Info.1234.QBW.nd
Exception '[Errno 13] Permission denied: 'c:/Sepco-Data/Shared-docs/Abc/Speedy Spooner 
 Forker Service.GWC..QBW'' raised of class 'type 'exceptions.IOError'':
  File rdiff_backup\robust.pyc, line 32, in check_common_error
  File rdiff_backup\Rdiff.pyc, line 61, in get_delta_sigrp_hash
  File rdiff_backup\rpath.pyc, line 1174, in open

Processing changed file Shared-docs/Abc/Speedy Spooner  Forker Service.GWC..QBW
Regular copying ('Shared-docs', 'Abc', 'Speedy Spooner  Forker 
Service.GWC..QBW') to e:/sepco-data/Shared-docs/Abc/rdiff-backup.tmp.10745
Incrementing mirror file e:/sepco-data/Shared-docs/Abc/Speedy Spooner  Forker 
Service.GWC..QBW
Regular copying ('Shared-docs', 'Abc', 'Speedy Spooner  Forker Service.GWC..QBW') 
to e:/sepco-data/rdiff-backup-data/increments/Shared-docs/Abc/Speedy Spooner  
Forker Service.GWC..QBW.2009-05-21T20-00-02-07-00.snapshot.gz
Backup pass finished at: 2009-05-29-Fri-20.18.28

---
What's odd is that it claims it finished the backup pass, but
rdiff-backup exits with a 255 code.

It also regresses the next backup before starting, so clearly it
doesn't think it ended correctly not-withstanding the log.

---
Help!

Details:
RDiff-Backup 1.3.3 on Windows, using windows native binary.
Source and Dest are local sata disks.
NTFS partitions on both systems.
TIA!
-Greg



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
  




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error installing 1.2.8

[Bob Mead]

Hi all:
I have an Ubuntu 8.10 system with rdiff v1.1.16 installed. Using the 
recipe on the wiki: 
http://wiki.rdiff-backup.org/wiki/index.php/Installations#Concurrent_installation_of_different_versions_of_rdiff-backup


and making the appropriate changes to the version number, I got an error 
when trying to install v.1.2.8 at the 'python setup.py build' part of 
the install. First it complained about not finding gcc - so I apt-get 
install[ed] gcc. then when I ran the 'build' cmd again, it errored out. 
I tried removing the rdiff-backup-1.2.8 directory and re-installing from 
the tarball, but I got the following error when I ran the 'build' cmd:


gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c cmodule.c -o 
build/temp.linux-i686-2.5/cmodule.o

cmodule.c:24:20: error: Python.h: No such file or directory
cmodule.c:76: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:77: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:78: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:79: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:80: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:84: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:86: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token

cmodule.c:87: error: expected identifier or ‘(’ before ‘{’ token
cmodule.c:217: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:219: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token

cmodule.c:220: error: expected identifier or ‘(’ before ‘{’ token
cmodule.c:233: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:235: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token

cmodule.c:236: error: expected identifier or ‘(’ before ‘{’ token
cmodule.c:244: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:246: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token

cmodule.c:247: error: expected identifier or ‘(’ before ‘{’ token
cmodule.c:364: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:373: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘*’ token
cmodule.c:416: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ 
before ‘CMethods’

cmodule.c: In function ‘initC’:
cmodule.c:435: error: ‘PyObject’ undeclared (first use in this function)
cmodule.c:435: error: (Each undeclared identifier is reported only once
cmodule.c:435: error: for each function it appears in.)
cmodule.c:435: error: ‘m’ undeclared (first use in this function)
cmodule.c:435: error: ‘d’ undeclared (first use in this function)
cmodule.c:435: warning: left-hand operand of comma expression has no effect
cmodule.c:437: warning: implicit declaration of function ‘Py_InitModule’
cmodule.c:437: error: ‘CMethods’ undeclared (first use in this function)
cmodule.c:438: warning: implicit declaration of function ‘PyModule_GetDict’
cmodule.c:439: error: ‘UnknownFileTypeError’ undeclared (first use in 
this function)
cmodule.c:439: warning: implicit declaration of function 
‘PyErr_NewException’
cmodule.c:441: warning: implicit declaration of function 
‘PyDict_SetItemString’

error: command 'gcc' failed with exit status 1

Please any help would be greatly appreciated. I am trying to upgrade my 
rdiff version to see if a newer version can overcome a 'warning: 
extended attributes file not found' error which v1.1.16 has been 
generating. Andrew's notes from the 1.2.7 release say that this was 
fixed there.


Thanks,
~bob
begin:vcard
fn:Bob Mead
n:Mead;Bob
org:South Lane School District;Technology Services Center
email;internet:bm...@lane.k12.or.us
title:Network Specialist
tel;work:541.762.1124
version:2.1
end:vcard

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error installing 1.2.8

[Bob Mead]

Hi Josh:
Thanks for the suggestion. I installed python-dev (curious: why was this 
not installed as part of the original v1.1.16 installation?), re-ran the 
'build' cmd. - it errored out so I rm-r the build dir. and tried again. 
It works until:

snip
building 'rdiff_backup._librsync' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c _librsyncmodule.c 
-o build/temp.linux-i686-2.5/_librsyncmodule.o

_librsyncmodule.c:25:22: error: librsync.h: No such file or directory
_librsyncmodule.c:32: error: expected ‘)’ before ‘result’
_librsyncmodule.c:46: error: expected specifier-qualifier-list before 
‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_sigmaker’:
_librsyncmodule.c:62: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:62: warning: implicit declaration of function 
‘rs_sig_begin’
_librsyncmodule.c:63: error: ‘RS_DEFAULT_STRONG_LEN’ undeclared (first 
use in this function)
_librsyncmodule.c:63: error: (Each undeclared identifier is reported 
only once

_librsyncmodule.c:63: error: for each function it appears in.)
_librsyncmodule.c: In function ‘_librsync_sigmaker_dealloc’:
_librsyncmodule.c:70: warning: implicit declaration of function 
‘rs_job_free’
_librsyncmodule.c:70: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’

_librsyncmodule.c: In function ‘_librsync_sigmaker_cycle’:
_librsyncmodule.c:84: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:84: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:85: error: ‘rs_result’ undeclared (first use in this 
function)

_librsyncmodule.c:85: error: expected ‘;’ before ‘result’
_librsyncmodule.c:90: error: ‘buf’ undeclared (first use in this function)
_librsyncmodule.c:96: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:96: warning: implicit declaration of function 
‘rs_job_iter’
_librsyncmodule.c:96: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:98: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:98: error: ‘RS_BLOCKED’ undeclared (first use in this 
function)
_librsyncmodule.c:99: warning: implicit declaration of function 
‘_librsync_seterror’

_librsyncmodule.c: At top level:
_librsyncmodule.c:171: error: expected specifier-qualifier-list before 
‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_deltamaker’:
_librsyncmodule.c:182: error: ‘rs_job_t’ undeclared (first use in this 
function)
_librsyncmodule.c:182: error: ‘sig_loader’ undeclared (first use in this 
function)
_librsyncmodule.c:183: error: ‘rs_signature_t’ undeclared (first use in 
this function)
_librsyncmodule.c:183: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:184: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:184: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:185: error: ‘rs_result’ undeclared (first use in this 
function)

_librsyncmodule.c:185: error: expected ‘;’ before ‘result’
_librsyncmodule.c:195: warning: implicit declaration of function 
‘rs_loadsig_begin’

_librsyncmodule.c:196: error: ‘buf’ undeclared (first use in this function)
_librsyncmodule.c:201: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:203: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:207: warning: implicit declaration of function 
‘rs_build_hash_table’
_librsyncmodule.c:212: error: ‘_librsync_DeltaMakerObject’ has no member 
named ‘sig_ptr’
_librsyncmodule.c:213: error: ‘_librsync_DeltaMakerObject’ has no member 
named ‘delta_job’
_librsyncmodule.c:213: warning: implicit declaration of function 
‘rs_delta_begin’

_librsyncmodule.c: In function ‘_librsync_deltamaker_dealloc’:
_librsyncmodule.c:221: error: ‘rs_signature_t’ undeclared (first use in 
this function)
_librsyncmodule.c:221: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:221: error: ‘_librsync_DeltaMakerObject’ has no member 
named ‘sig_ptr’
_librsyncmodule.c:223: warning: implicit declaration of function 
‘rs_free_sumset’
_librsyncmodule.c:224: error: ‘_librsync_DeltaMakerObject’ has no member 
named ‘delta_job’

_librsyncmodule.c: In function ‘_librsync_deltamaker_cycle’:
_librsyncmodule.c:238: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:238: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:239: error: ‘rs_result’ undeclared (first use in this 
function)

_librsyncmodule.c:239: error: expected ‘;’ before ‘result’
_librsyncmodule.c:244: error: ‘buf’ undeclared (first use in this function)
_librsyncmodule.c:250: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:250: error: ‘_librsync_DeltaMakerObject’ has no member 
named ‘delta_job’
_librsyncmodule.c:251: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:251: error: ‘RS_BLOCKED’ undeclared 

Re: [rdiff-backup-users] Error installing 1.2.8

[Bob Mead]

got it. needed librsync-dev as well. still curious as to why these two 
packages weren't already installed with v1.1.16?

Thanks,
   ~bob

Bob Mead wrote:

Hi Josh:
Thanks for the suggestion. I installed python-dev (curious: why was 
this not installed as part of the original v1.1.16 installation?), 
re-ran the 'build' cmd. - it errored out so I rm-r the build dir. and 
tried again. It works until:

snip
building 'rdiff_backup._librsync' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c 
_librsyncmodule.c -o build/temp.linux-i686-2.5/_librsyncmodule.o

_librsyncmodule.c:25:22: error: librsync.h: No such file or directory
_librsyncmodule.c:32: error: expected ‘)’ before ‘result’
_librsyncmodule.c:46: error: expected specifier-qualifier-list before 
‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_sigmaker’:
_librsyncmodule.c:62: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:62: warning: implicit declaration of function 
‘rs_sig_begin’
_librsyncmodule.c:63: error: ‘RS_DEFAULT_STRONG_LEN’ undeclared (first 
use in this function)
_librsyncmodule.c:63: error: (Each undeclared identifier is reported 
only once

_librsyncmodule.c:63: error: for each function it appears in.)
_librsyncmodule.c: In function ‘_librsync_sigmaker_dealloc’:
_librsyncmodule.c:70: warning: implicit declaration of function 
‘rs_job_free’
_librsyncmodule.c:70: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’

_librsyncmodule.c: In function ‘_librsync_sigmaker_cycle’:
_librsyncmodule.c:84: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:84: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:85: error: ‘rs_result’ undeclared (first use in this 
function)

_librsyncmodule.c:85: error: expected ‘;’ before ‘result’
_librsyncmodule.c:90: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:96: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:96: warning: implicit declaration of function 
‘rs_job_iter’
_librsyncmodule.c:96: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:98: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:98: error: ‘RS_BLOCKED’ undeclared (first use in 
this function)
_librsyncmodule.c:99: warning: implicit declaration of function 
‘_librsync_seterror’

_librsyncmodule.c: At top level:
_librsyncmodule.c:171: error: expected specifier-qualifier-list before 
‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_deltamaker’:
_librsyncmodule.c:182: error: ‘rs_job_t’ undeclared (first use in this 
function)
_librsyncmodule.c:182: error: ‘sig_loader’ undeclared (first use in 
this function)
_librsyncmodule.c:183: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:183: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:184: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:184: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:185: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:185: error: expected ‘;’ before ‘result’
_librsyncmodule.c:195: warning: implicit declaration of function 
‘rs_loadsig_begin’
_librsyncmodule.c:196: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:201: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:203: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:207: warning: implicit declaration of function 
‘rs_build_hash_table’
_librsyncmodule.c:212: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:213: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’
_librsyncmodule.c:213: warning: implicit declaration of function 
‘rs_delta_begin’

_librsyncmodule.c: In function ‘_librsync_deltamaker_dealloc’:
_librsyncmodule.c:221: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:221: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:221: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:223: warning: implicit declaration of function 
‘rs_free_sumset’
_librsyncmodule.c:224: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’

_librsyncmodule.c: In function ‘_librsync_deltamaker_cycle’:
_librsyncmodule.c:238: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:238: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:239: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:239: error: expected ‘;’ before ‘result’
_librsyncmodule.c:244: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:250: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:250: error: ‘_librsync_DeltaMakerObject’ has no 

Re: [rdiff-backup-users] Error installing 1.2.8

[Josh Nisly]

The reason that those packages weren't needed before is that (IIUC) you 
installed the binary packages. It was only once you tried to build 
rdiff-backup from source that you needed the development files for 
python and librsync.


JoshN

Bob Mead wrote:
got it. needed librsync-dev as well. still curious as to why these two 
packages weren't already installed with v1.1.16?

Thanks,
   ~bob

Bob Mead wrote:

Hi Josh:
Thanks for the suggestion. I installed python-dev (curious: why was 
this not installed as part of the original v1.1.16 installation?), 
re-ran the 'build' cmd. - it errored out so I rm-r the build dir. and 
tried again. It works until:

snip
building 'rdiff_backup._librsync' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c 
_librsyncmodule.c -o build/temp.linux-i686-2.5/_librsyncmodule.o

_librsyncmodule.c:25:22: error: librsync.h: No such file or directory
_librsyncmodule.c:32: error: expected ‘)’ before ‘result’
_librsyncmodule.c:46: error: expected specifier-qualifier-list before 
‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_sigmaker’:
_librsyncmodule.c:62: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:62: warning: implicit declaration of function 
‘rs_sig_begin’
_librsyncmodule.c:63: error: ‘RS_DEFAULT_STRONG_LEN’ undeclared 
(first use in this function)
_librsyncmodule.c:63: error: (Each undeclared identifier is reported 
only once

_librsyncmodule.c:63: error: for each function it appears in.)
_librsyncmodule.c: In function ‘_librsync_sigmaker_dealloc’:
_librsyncmodule.c:70: warning: implicit declaration of function 
‘rs_job_free’
_librsyncmodule.c:70: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’

_librsyncmodule.c: In function ‘_librsync_sigmaker_cycle’:
_librsyncmodule.c:84: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:84: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:85: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:85: error: expected ‘;’ before ‘result’
_librsyncmodule.c:90: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:96: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:96: warning: implicit declaration of function 
‘rs_job_iter’
_librsyncmodule.c:96: error: ‘_librsync_SigMakerObject’ has no member 
named ‘sig_job’
_librsyncmodule.c:98: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:98: error: ‘RS_BLOCKED’ undeclared (first use in 
this function)
_librsyncmodule.c:99: warning: implicit declaration of function 
‘_librsync_seterror’

_librsyncmodule.c: At top level:
_librsyncmodule.c:171: error: expected specifier-qualifier-list 
before ‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_deltamaker’:
_librsyncmodule.c:182: error: ‘rs_job_t’ undeclared (first use in 
this function)
_librsyncmodule.c:182: error: ‘sig_loader’ undeclared (first use in 
this function)
_librsyncmodule.c:183: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:183: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:184: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:184: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:185: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:185: error: expected ‘;’ before ‘result’
_librsyncmodule.c:195: warning: implicit declaration of function 
‘rs_loadsig_begin’
_librsyncmodule.c:196: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:201: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:203: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:207: warning: implicit declaration of function 
‘rs_build_hash_table’
_librsyncmodule.c:212: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:213: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’
_librsyncmodule.c:213: warning: implicit declaration of function 
‘rs_delta_begin’

_librsyncmodule.c: In function ‘_librsync_deltamaker_dealloc’:
_librsyncmodule.c:221: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:221: error: ‘sig_ptr’ undeclared (first use in this 
function)
_librsyncmodule.c:221: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:223: warning: implicit declaration of function 
‘rs_free_sumset’
_librsyncmodule.c:224: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’

_librsyncmodule.c: In function ‘_librsync_deltamaker_cycle’:
_librsyncmodule.c:238: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:238: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:239: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:239: error: 

Re: [rdiff-backup-users] Error installing 1.2.8

[Bob Mead]

Thanks Josh. I've updated the wiki page to add this information.
   ~bob

Josh Nisly wrote:
The reason that those packages weren't needed before is that (IIUC) 
you installed the binary packages. It was only once you tried to build 
rdiff-backup from source that you needed the development files for 
python and librsync.


JoshN

Bob Mead wrote:
got it. needed librsync-dev as well. still curious as to why these 
two packages weren't already installed with v1.1.16?

Thanks,
   ~bob

Bob Mead wrote:

Hi Josh:
Thanks for the suggestion. I installed python-dev (curious: why was 
this not installed as part of the original v1.1.16 installation?), 
re-ran the 'build' cmd. - it errored out so I rm-r the build dir. 
and tried again. It works until:

snip
building 'rdiff_backup._librsync' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.5 -c 
_librsyncmodule.c -o build/temp.linux-i686-2.5/_librsyncmodule.o

_librsyncmodule.c:25:22: error: librsync.h: No such file or directory
_librsyncmodule.c:32: error: expected ‘)’ before ‘result’
_librsyncmodule.c:46: error: expected specifier-qualifier-list 
before ‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_sigmaker’:
_librsyncmodule.c:62: error: ‘_librsync_SigMakerObject’ has no 
member named ‘sig_job’
_librsyncmodule.c:62: warning: implicit declaration of function 
‘rs_sig_begin’
_librsyncmodule.c:63: error: ‘RS_DEFAULT_STRONG_LEN’ undeclared 
(first use in this function)
_librsyncmodule.c:63: error: (Each undeclared identifier is reported 
only once

_librsyncmodule.c:63: error: for each function it appears in.)
_librsyncmodule.c: In function ‘_librsync_sigmaker_dealloc’:
_librsyncmodule.c:70: warning: implicit declaration of function 
‘rs_job_free’
_librsyncmodule.c:70: error: ‘_librsync_SigMakerObject’ has no 
member named ‘sig_job’

_librsyncmodule.c: In function ‘_librsync_sigmaker_cycle’:
_librsyncmodule.c:84: error: ‘rs_buffers_t’ undeclared (first use in 
this function)

_librsyncmodule.c:84: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:85: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:85: error: expected ‘;’ before ‘result’
_librsyncmodule.c:90: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:96: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:96: warning: implicit declaration of function 
‘rs_job_iter’
_librsyncmodule.c:96: error: ‘_librsync_SigMakerObject’ has no 
member named ‘sig_job’
_librsyncmodule.c:98: error: ‘RS_DONE’ undeclared (first use in this 
function)
_librsyncmodule.c:98: error: ‘RS_BLOCKED’ undeclared (first use in 
this function)
_librsyncmodule.c:99: warning: implicit declaration of function 
‘_librsync_seterror’

_librsyncmodule.c: At top level:
_librsyncmodule.c:171: error: expected specifier-qualifier-list 
before ‘rs_job_t’

_librsyncmodule.c: In function ‘_librsync_new_deltamaker’:
_librsyncmodule.c:182: error: ‘rs_job_t’ undeclared (first use in 
this function)
_librsyncmodule.c:182: error: ‘sig_loader’ undeclared (first use in 
this function)
_librsyncmodule.c:183: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:183: error: ‘sig_ptr’ undeclared (first use in 
this function)
_librsyncmodule.c:184: error: ‘rs_buffers_t’ undeclared (first use 
in this function)

_librsyncmodule.c:184: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:185: error: ‘rs_result’ undeclared (first use in 
this function)

_librsyncmodule.c:185: error: expected ‘;’ before ‘result’
_librsyncmodule.c:195: warning: implicit declaration of function 
‘rs_loadsig_begin’
_librsyncmodule.c:196: error: ‘buf’ undeclared (first use in this 
function)
_librsyncmodule.c:201: error: ‘result’ undeclared (first use in this 
function)
_librsyncmodule.c:203: error: ‘RS_DONE’ undeclared (first use in 
this function)
_librsyncmodule.c:207: warning: implicit declaration of function 
‘rs_build_hash_table’
_librsyncmodule.c:212: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:213: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’
_librsyncmodule.c:213: warning: implicit declaration of function 
‘rs_delta_begin’

_librsyncmodule.c: In function ‘_librsync_deltamaker_dealloc’:
_librsyncmodule.c:221: error: ‘rs_signature_t’ undeclared (first use 
in this function)
_librsyncmodule.c:221: error: ‘sig_ptr’ undeclared (first use in 
this function)
_librsyncmodule.c:221: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘sig_ptr’
_librsyncmodule.c:223: warning: implicit declaration of function 
‘rs_free_sumset’
_librsyncmodule.c:224: error: ‘_librsync_DeltaMakerObject’ has no 
member named ‘delta_job’

_librsyncmodule.c: In function ‘_librsync_deltamaker_cycle’:
_librsyncmodule.c:238: error: ‘rs_buffers_t’ undeclared (first use 
in this function)

_librsyncmodule.c:238: error: expected ‘;’ before ‘buf’
_librsyncmodule.c:239: 

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Nathan Aschbacher]

Well I managed to get SMB access working somehow.  A combination of  
unix extensions = no in the global space of my samba configuration,  
building the proper driver for my NIC on the linux server, and luck.


I also got netatalk setup and running for AFP access, and installed  
rdiff-backup on the server to try the direct SSH method.


My findings were interesting:

Client:
Apple MacBook (unibody) 2.4Ghz 4gig RAM w/ 320GB Hitachi  
HTS543232L9A300 drive; Mac OS X 10.5.6


Server:
MSI Wind Nettop (2x core Atom 330) 1.6Ghz 2gig RAM w/ 2x 1TB Samsung  
Spinpoint F1's, mirrored via mdadm, ext4 filesystem; Ubuntu 9.04 beta


Network:
Gigabit ethernet on both ends connected via Netgear Gig-E switch, MTU  
on both machines set to 6144 (the highest the MSI's NIC will handle)


Test File Set:
2.91 Gigs, 1748 files, a mix of CD image ISO's, media files (audo/ 
video), and tons of very small documents/resources/source-files


Results: (times are in min:sec)

Initial Backup  Peak Throughput Next Backup (no changed 
files)
SMB  -  8:02~12 MB/s
0:25
AFP  -  3:28~38 MB/s
0:10
SSH  -  8:36~8 MB/s 
0:21
local - 3:33~27 MB/s
0:09

In standard file copying Samba is typically much closer in performance  
than that, it's usually only a few MB/s slower than netatalk.
Typical data rate for direct copying a large contiguous 1 GB file with  
this setup is ~43 MB/s for AFP, ~39 MB/s for SMB, and ~17 MB/s for SSH  
(scp).  Going to the AFP share was essentially as fast as performing  
the backup where the target was the same local disk as the source (of  
course performance would be better if using an external drive, but  
still).


In that sense I can understand why SSH is so slow, it has all the  
encrypt/decrypt overhead going on, as well as compression being  
performed.  The only thing I can think to explain the massive  
disparity between SMB and AFP using rdiff-backup is how each one deals  
with Mac OS X specific data like resource forks, etc.  When using AFP,  
netatalk is handling all of the Mac-specific data, when using SMB,  
rdiff-backup is handling it.  Not surprisingly netatalk is more  
efficient in that regard.


I suspect these massive discrepancies in performance are largely Mac- 
specific because of the odd filesystem features that have to be  
recreated via one means or another on the target filesystem.  However,  
it was interesting to see the massive difference in performance.   
Needless to say, based on these tests, I'll be sticking with AFP for  
my rdiff-backups, and finally ditching Time Machine!


I hope this information is helpful to somebody someday.

Cheers!
-Nathan



On Mar 29, 2009, at 2:25 PM, Andrew Ferguson wrote:



On Mar 29, 2009, at 12:33 PM, Nathan Aschbacher wrote:
The rm tgt fails, well not exactly.  It runs without an error the  
first time, but some kind of problem occurs on OS X where the file  
won't stay deleted, it immediately reappears.  Once it reappears  
two problems occur.  First, if you try to delete it again the  
system claims it doesn't exist, secondly any check that looks to  
see if the directory is empty will fail (because ls still returns  
tgt).  The symlink tgt has to be delete by logging into the Samba  
server.  If I connect to the same share from an Ubuntu desktop and  
try the same set of operations through the GUI it won't let me even  
create the symlink, claiming that the target volume doesn't support  
it.  It seems like there's some very strange interaction occurring  
between Mac OS X and the Samba share.  You gotta love Apple's  
spectacularly bad Samba implementation.


That description is consistent with the stack trace from rdiff- 
backup. The trace points to a file deletion error when attempting to  
clear out the temporary directory in which it had tested filesystem  
abilities, such as symlinks.


It's certainly a strange situation... I've never heard of that  
sequence of events happening before. Of course, it doesn't help that  
there are so many ways in which the Samba server can be configured.


Have you considered other network filesystems such as NFS or  
Appleshare/Netatalk? Of course, installing rdiff-backup on the  
server and running over SSH will be the fastest, performance-wise.



Andrew


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: 

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Andrew Ferguson]

Hi Nathan,

Thanks so much for doing the testing. I had not expected those  
results. Of course, the more interesting test is when you do a backup  
in which there are dozens of changes scattered across the files. That  
is where the rsync algorithm is supposed to be helpful -- it trades  
network bandwidth for CPU. With rdiff-backup running over SSH, only  
the changes to the files will be transmitted over the network, whereas  
with rdiff-backup running over SMB or AFP, the whole file will be sent  
over the network. See: http://en.wikipedia.org/wiki/Rsync


Also, when you do the initial backup, what happens if you add the -- 
ssh-no-compression option to rdiff-backup?



Thanks!

Andrew


On Mar 30, 2009, at 3:35 AM, Nathan Aschbacher wrote:

Well I managed to get SMB access working somehow.  A combination of  
unix extensions = no in the global space of my samba  
configuration, building the proper driver for my NIC on the linux  
server, and luck.


I also got netatalk setup and running for AFP access, and installed  
rdiff-backup on the server to try the direct SSH method.


My findings were interesting:

Client:
Apple MacBook (unibody) 2.4Ghz 4gig RAM w/ 320GB Hitachi  
HTS543232L9A300 drive; Mac OS X 10.5.6


Server:
MSI Wind Nettop (2x core Atom 330) 1.6Ghz 2gig RAM w/ 2x 1TB Samsung  
Spinpoint F1's, mirrored via mdadm, ext4 filesystem; Ubuntu 9.04 beta


Network:
Gigabit ethernet on both ends connected via Netgear Gig-E switch,  
MTU on both machines set to 6144 (the highest the MSI's NIC will  
handle)


Test File Set:
2.91 Gigs, 1748 files, a mix of CD image ISO's, media files (audo/ 
video), and tons of very small documents/resources/source-files


Results: (times are in min:sec)

Initial Backup  Peak Throughput Next Backup (no changed 
files)
SMB  -  8:02~12 MB/s
0:25
AFP  -  3:28~38 MB/s
0:10
SSH  -  8:36~8 MB/s 
0:21
local - 3:33~27 MB/s
0:09

In standard file copying Samba is typically much closer in  
performance than that, it's usually only a few MB/s slower than  
netatalk.   Typical data rate for direct copying a large contiguous  
1 GB file with this setup is ~43 MB/s for AFP, ~39 MB/s for SMB, and  
~17 MB/s for SSH (scp).  Going to the AFP share was essentially as  
fast as performing the backup where the target was the same local  
disk as the source (of course performance would be better if using  
an external drive, but still).


In that sense I can understand why SSH is so slow, it has all the  
encrypt/decrypt overhead going on, as well as compression being  
performed.  The only thing I can think to explain the massive  
disparity between SMB and AFP using rdiff-backup is how each one  
deals with Mac OS X specific data like resource forks, etc.  When  
using AFP, netatalk is handling all of the Mac-specific data, when  
using SMB, rdiff-backup is handling it.  Not surprisingly netatalk  
is more efficient in that regard.


I suspect these massive discrepancies in performance are largely Mac- 
specific because of the odd filesystem features that have to be  
recreated via one means or another on the target filesystem.   
However, it was interesting to see the massive difference in  
performance.  Needless to say, based on these tests, I'll be  
sticking with AFP for my rdiff-backups, and finally ditching Time  
Machine!


I hope this information is helpful to somebody someday.

Cheers!
-Nathan



On Mar 29, 2009, at 2:25 PM, Andrew Ferguson wrote:



On Mar 29, 2009, at 12:33 PM, Nathan Aschbacher wrote:
The rm tgt fails, well not exactly.  It runs without an error  
the first time, but some kind of problem occurs on OS X where the  
file won't stay deleted, it immediately reappears.  Once it  
reappears two problems occur.  First, if you try to delete it  
again the system claims it doesn't exist, secondly any check that  
looks to see if the directory is empty will fail (because ls  
still returns tgt).  The symlink tgt has to be delete by logging  
into the Samba server.  If I connect to the same share from an  
Ubuntu desktop and try the same set of operations through the GUI  
it won't let me even create the symlink, claiming that the target  
volume doesn't support it.  It seems like there's some very  
strange interaction occurring between Mac OS X and the Samba  
share.  You gotta love Apple's spectacularly bad Samba  
implementation.


That description is consistent with the stack trace from rdiff- 
backup. The trace points to a file deletion error when attempting  
to clear out the temporary directory in which it had tested  
filesystem abilities, such as symlinks.


It's certainly a strange situation... I've never heard of that  
sequence of events 

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Nathan Aschbacher]

Hi Andrew,

Sorry for the delay.  I tried to run it with 1.3.3 and here's what I  
got:


HotPlate:~ nathan$ rdiff-backup -v 5 ~/Desktop/ /Volumes/Insurance/ 
Backup/

Using rdiff-backup version 1.3.3
Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Users/nathan/Desktop
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Users/nathan/Desktop
-
Detected abilities for source (read only) file system:
  Access control lists Off
  Extended attributes  On
  Windows access control lists Off
  Case sensitivity Off
  Escape DOS devices   Off
  Escape trailing spaces   Off
  Mac OS X style resource forksOn
  Mac OS X Finder information  On
-
Warning: hard linking not supported by filesystem at /Volumes/ 
Insurance/Backup/rdiff-backup-data

Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Volumes/Insurance/Backup/ 
rdiff-backup-data/rdiff-backup.tmp.0

Unable to import win32security module. Windows ACLs
not supported by filesystem at /Volumes/Insurance/Backup/rdiff-backup- 
data/rdiff-backup.tmp.0
Exception '[Errno 2] No such file or directory: '/Volumes/Insurance/ 
Backup/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'' raised  
of class 'type 'exceptions.OSError'':
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 306, in  
error_check_Main

try: Main(arglist)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 326, in Main

take_action(rps)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 282, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 336, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/fs_abilities.py, line 959, in  
backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/fs_abilities.py, line 171, in  
init_readwrite

subdir.delete()
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/rpath.py, line 1070, in delete

self.conn.shutil.rmtree(self.path)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/shutil.py, line 221, in rmtree

onerror(os.remove, fullname, sys.exc_info())
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/shutil.py, line 219, in rmtree

os.remove(fullname)

Traceback (most recent call last):
  File /usr/local/bin/rdiff-backup, line 30, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 306, in  
error_check_Main

try: Main(arglist)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 326, in Main

take_action(rps)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 282, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/Main.py, line 336, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/fs_abilities.py, line 959, in  
backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/fs_abilities.py, line 171, in  
init_readwrite

subdir.delete()
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/rdiff_backup/rpath.py, line 1070, in delete

self.conn.shutil.rmtree(self.path)
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/shutil.py, line 221, in rmtree

onerror(os.remove, fullname, sys.exc_info())
  File /Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/shutil.py, line 219, in rmtree

os.remove(fullname)
OSError: [Errno 2] No such file or directory: '/Volumes/Insurance/ 
Backup/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'


Now the interesting thing is that I think I 

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Andrew Ferguson]

On Mar 29, 2009, at 12:33 PM, Nathan Aschbacher wrote:
The rm tgt fails, well not exactly.  It runs without an error the  
first time, but some kind of problem occurs on OS X where the file  
won't stay deleted, it immediately reappears.  Once it reappears two  
problems occur.  First, if you try to delete it again the system  
claims it doesn't exist, secondly any check that looks to see if the  
directory is empty will fail (because ls still returns tgt).  The  
symlink tgt has to be delete by logging into the Samba server.  If  
I connect to the same share from an Ubuntu desktop and try the same  
set of operations through the GUI it won't let me even create the  
symlink, claiming that the target volume doesn't support it.  It  
seems like there's some very strange interaction occurring between  
Mac OS X and the Samba share.  You gotta love Apple's spectacularly  
bad Samba implementation.


That description is consistent with the stack trace from rdiff-backup.  
The trace points to a file deletion error when attempting to clear out  
the temporary directory in which it had tested filesystem abilities,  
such as symlinks.


It's certainly a strange situation... I've never heard of that  
sequence of events happening before. Of course, it doesn't help that  
there are so many ways in which the Samba server can be configured.


Have you considered other network filesystems such as NFS or  
Appleshare/Netatalk? Of course, installing rdiff-backup on the server  
and running over SSH will be the fastest, performance-wise.



Andrew


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Andrew Ferguson]

On Mar 20, 2009, at 6:44 PM, Nathan Aschbacher wrote:
I've tried several versions of rdiff-backup (up through 1.3.3) and  
several versions of Python (up through 2.6.1).  I believe the issues  
relates to symbolic links based on the error.  It seems to fail when  
doing its destination capability tests when it fails to delete the  
temp symlink.  When I go and look at what rdiff-backup creates  
before dying the file /Volumes/For_Rent/Desktop/rdiff-backup-data/ 
rdiff-backup.tmp.0/symlinked_file2 is a broken symlink to a file  
symlinked_file1 that doesn't exist.


Backups over SSH, using sshfs and MacFUSE, and to the local HD all  
work fine.  So this seems like a strange interaction between rdiff- 
backup and Samba.


Whenever I try to perform a backup to the samba share on my  
fileserver over smbfs from my Macbook I get the following error:


Nathans-MacBook:~ nathan$ rdiff-backup --force -v5 ~/Desktop/ / 
Volumes/For_Rent/Desktop/


Using rdiff-backup version 1.2.2



Hmm, I know you specified that you tried several versions, but can you  
paste the output from the latest version?


There were specific changes in 1.2.3 related exactly to the problem  
you are experiencing. That doesn't mean that the problem will go away,  
but I think the error should be different.




thanks,
Andrew

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Nathan Aschbacher]

I've tried several versions of rdiff-backup (up through 1.3.3) and  
several versions of Python (up through 2.6.1).  I believe the issues  
relates to symbolic links based on the error.  It seems to fail when  
doing its destination capability tests when it fails to delete the  
temp symlink.  When I go and look at what rdiff-backup creates before  
dying the file /Volumes/For_Rent/Desktop/rdiff-backup-data/rdiff- 
backup.tmp.0/symlinked_file2 is a broken symlink to a file  
symlinked_file1 that doesn't exist.


Backups over SSH, using sshfs and MacFUSE, and to the local HD all  
work fine.  So this seems like a strange interaction between rdiff- 
backup and Samba.


Whenever I try to perform a backup to the samba share on my fileserver  
over smbfs from my Macbook I get the following error:


Nathans-MacBook:~ nathan$ rdiff-backup --force -v5 ~/Desktop/ /Volumes/ 
For_Rent/Desktop/


Using rdiff-backup version 1.2.2
Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Users/nathan/Desktop
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Users/nathan/Desktop
escape_dos_devices not required by filesystem at /Users/nathan/Desktop
-
Detected abilities for source (read only) file system:
  Access control lists Off
  Extended attributes  On
  Windows access control lists Off
  Case sensitivity Off
  Escape DOS devices   Off
  Mac OS X style resource forksOn
  Mac OS X Finder information  On
-
Warning: hard linking not supported by filesystem at /Volumes/For_Rent/ 
Desktop/rdiff-backup-data

Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Volumes/For_Rent/Desktop/ 
rdiff-backup-data/rdiff-backup.tmp.0

Unable to import win32security module. Windows ACLs
not supported by filesystem at /Volumes/For_Rent/Desktop/rdiff-backup- 
data/rdiff-backup.tmp.0
Exception '[Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'' raised  
of class 'type 'exceptions.OSError'':
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)

Traceback (most recent call last):
  File /opt/local/bin/rdiff-backup, line 30, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)
OSError: [Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org

[rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Nathan Aschbacher]

I've tried several versions of rdiff-backup (up through 1.3.3) and  
several versions of Python (up through 2.6.1).  I believe the issues  
relates to symbolic links based on the error.  It seems to fail when  
doing its destination capability tests when it fails to delete the  
temp symlink.  When I go and look at what rdiff-backup creates before  
dying the file /Volumes/For_Rent/Desktop/rdiff-backup-data/rdiff- 
backup.tmp.0/symlinked_file2 is a broken symlink to a file  
symlinked_file1 that doesn't exist.


Backups over SSH, using sshfs and MacFUSE, and to the local HD all  
work fine.  So this seems like a strange interaction between rdiff- 
backup and Samba.


Whenever I try to perform a backup to the samba share on my fileserver  
over smbfs from my Macbook I get the following error:


Nathans-MacBook:~ nathan$ rdiff-backup --force -v5 ~/Desktop/ /Volumes/ 
For_Rent/Desktop/


Using rdiff-backup version 1.2.2
Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Users/nathan/Desktop
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Users/nathan/Desktop
escape_dos_devices not required by filesystem at /Users/nathan/Desktop
-
Detected abilities for source (read only) file system:
  Access control lists Off
  Extended attributes  On
  Windows access control lists Off
  Case sensitivity Off
  Escape DOS devices   Off
  Mac OS X style resource forksOn
  Mac OS X Finder information  On
-
Warning: hard linking not supported by filesystem at /Volumes/For_Rent/ 
Desktop/rdiff-backup-data

Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Volumes/For_Rent/Desktop/ 
rdiff-backup-data/rdiff-backup.tmp.0

Unable to import win32security module. Windows ACLs
not supported by filesystem at /Volumes/For_Rent/Desktop/rdiff-backup- 
data/rdiff-backup.tmp.0
Exception '[Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'' raised  
of class 'type 'exceptions.OSError'':
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)

Traceback (most recent call last):
  File /opt/local/bin/rdiff-backup, line 30, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)
OSError: [Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org

[rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Nathan Aschbacher]

I've tried several versions of rdiff-backup (up through 1.3.3) and  
several versions of Python (up through 2.6.1).  I believe the issues  
relates to symbolic links based on the error.  It seems to fail when  
doing its destination capability tests when it fails to delete the  
temp symlink.  When I go and look at what rdiff-backup creates before  
dying the file /Volumes/For_Rent/Desktop/rdiff-backup-data/rdiff- 
backup.tmp.0/symlinked_file2 is a broken symlink to a file  
symlinked_file1 that doesn't exist.


Backups over SSH, using sshfs and MacFUSE, and to the local HD all  
work fine.  So this seems like a strange interaction between rdiff- 
backup and Samba.


Whenever I try to perform a backup to the samba share on my fileserver  
over smbfs from my Macbook I get the following error:


Nathans-MacBook:~ nathan$ rdiff-backup --force -v5 ~/Desktop/ /Volumes/ 
For_Rent/Desktop/


Using rdiff-backup version 1.2.2
Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Users/nathan/Desktop
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Users/nathan/Desktop
escape_dos_devices not required by filesystem at /Users/nathan/Desktop
-
Detected abilities for source (read only) file system:
  Access control lists Off
  Extended attributes  On
  Windows access control lists Off
  Case sensitivity Off
  Escape DOS devices   Off
  Mac OS X style resource forksOn
  Mac OS X Finder information  On
-
Warning: hard linking not supported by filesystem at /Volumes/For_Rent/ 
Desktop/rdiff-backup-data

Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Volumes/For_Rent/Desktop/ 
rdiff-backup-data/rdiff-backup.tmp.0

Unable to import win32security module. Windows ACLs
not supported by filesystem at /Volumes/For_Rent/Desktop/rdiff-backup- 
data/rdiff-backup.tmp.0
Exception '[Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'' raised  
of class 'type 'exceptions.OSError'':
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)

Traceback (most recent call last):
  File /opt/local/bin/rdiff-backup, line 30, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 304, in error_check_Main

try: Main(arglist)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 324, in Main

take_action(rps)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 280, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/Main.py,  
line 334, in Backup

rpout.conn.fs_abilities.backup_set_globals(rpin, force)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 830, in backup_set_globals

dest_fsa = FSAbilities('destination').init_readwrite(Globals.rbdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 162, in init_readwrite

self.set_symlink_perms(subdir)
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
fs_abilities.py, line 539, in set_symlink_perms

sym_dest.delete()
  File /opt/local/lib/python2.5/site-packages/rdiff_backup/ 
rpath.py, line 1055, in delete

else: self.conn.os.unlink(self.path)
OSError: [Errno 2] No such file or directory: '/Volumes/For_Rent/ 
Desktop/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2'


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org

Re: [rdiff-backup-users] Error When Backing up to samba share on ubuntu 8.10 via smbfs on Mac OS X

[Andrew Ferguson]

On Mar 20, 2009, at 6:44 PM, Nathan Aschbacher wrote:

I've tried several versions of rdiff-backup (up through 1.3.3) and  
several versions of Python (up through 2.6.1).  I believe the issues  
relates to symbolic links based on the error.  It seems to fail when  
doing its destination capability tests when it fails to delete the  
temp symlink.  When I go and look at what rdiff-backup creates  
before dying the file /Volumes/For_Rent/Desktop/rdiff-backup-data/ 
rdiff-backup.tmp.0/symlinked_file2 is a broken symlink to a file  
symlinked_file1 that doesn't exist.


Backups over SSH, using sshfs and MacFUSE, and to the local HD all  
work fine.  So this seems like a strange interaction between rdiff- 
backup and Samba.



Yes, Samba is pretty bad at consistency (which is an open research  
area for network file systems). As you can see from the FAQ, getting  
Samba to work on Linux requires adjusting several options:

http://www.nongnu.org/rdiff-backup/FAQ.html#cifs

Since Mac OS X doesn't give you those options (at least that I'm aware  
of), you'll need to adjust parameters on the server.


This problem also occured when Mac OS X was mounting AFP shares...
http://lists.nongnu.org/archive/html/rdiff-backup-users/2007-06/msg00036.html

(that thread has some useful debugging tests you can run.)

Finally, let me emphasize what it says in the FAQ: If possible, the  
best solution is always to use rdiff-backup over SSH in the default  
configuration. Using rdiff-backup in the default configuration is also  
guaranteed to be faster because there is lower network utilization.  
Rdiff-backup uses the rsync algorithm to minimize the amount of  
bandwidth consumed. By using smbfs or CIFS, the complete file is  
transferred over the network.



Andrew___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error 22 -- rdiff-backup 1.2.5 OS X

[sphen]

weird -- the ls command on 10.4.11 doesnt have the -@ switch...  so i
attempted to use rsync 3 with the -X switchto transfer and got the same
error:

sending incremental file list
rsync: get_xattr_names: llistxattr(duraseal/RequestADemo.html,1024)
failed: Invalid argument (22)
rsync: get_xattr_names: llistxattr(duraseal/Comps/index.psd,1024) failed:
Invalid argument (22)
rsync: get_xattr_names: llistxattr(duraseal/Comps/inside.psd,1024) failed:
Invalid argument (22)
rsync: get_xattr_names: llistxattr(duraseal/Comps/landing.psd,1024)
failed: Invalid argument (22)
duraseal/

strange...  so it looks like the files itself maybe are locked?  i have
never had rsync fail on a file before...  i can try and see if there is a
way to trim the xattr from the files and try again.  and yes this is 10.4.11
server on the sending side...


Andrew Ferguson-4 wrote:
 
 Hi Sphen,
 
 Strange error ... Each time, it comes when rdiff-backup is asking for  
 a list of the extended attributes on those 4 files.
 
 What does `file` and `ls -...@e` report on each of those files?
 
 /Library/WebServer/Documents/duraseal/Comps/index.psd
 /Library/WebServer/Documents/duraseal/Comps/inside.psd
 /Library/WebServer/Documents/duraseal/Comps/landing.psd
 /Library/WebServer/Documents/duraseal/RequestADemo.html
 
 
 And, just to confirm, this is on the 10.4.11 server, yes? I wonder  
 what would happen if you copy those files to the 10.5.6 server and try  
 again...
 
 
 thanks,
 Andrew
 
 
 On Jan 14, 2009, at 7:10 PM, sphen boyle wrote:
 
 hi there..

 just installed rdiff-backup on a couple machines (one on server  
 10.5.6 python 2.5.1 and  one on server 10.4.11 python 2.3)  --  
 everything worked fine upon first backup - but is throwing some  
 errors on 4 files upon subsequent ones.  nothing too crazy with the  
 setup that i am aware of. the command i am running is as follows:

 rdiff-backup -v5 --remote-schema 'ssh -c arcfour -C %s  rdiff- 
 backup  --server' --print-statistics /Library/WebServer
 r...@192.168.254.244 
 ::/Volumes/Storage/rdiff/WebServer

 the following is what is put out to the logfile.  other files do  
 seem to increment fine - but ive only ran the backup a few times...   
 please let me know if there is any more information that i can give  
 to narrow this down.  thanks!

 Using rdiff-backup version 1.2.5
 Executing ssh -C r...@192.168.254.244 rdiff-backup --server
 No increments older than Sat Nov 15 16:34:31 2008 found, exiting.
 Using rdiff-backup version 1.2.5
 Executing ssh -c arcfour -C r...@192.168.254.244  rdiff-backup  -- 
 server
 Unable to import module posix1e from pylibacl package.
 POSIX ACLs not supported on filesystem at /Library/WebServer
 Unable to import win32security module. Windows ACLs
 not supported by filesystem at /Library/WebServer
 escape_dos_devices not required by filesystem at /Library/WebServer
 Starting increment operation /Library/WebServer to /Volumes/Storage/ 
 rdiff/WebServer
 Exception '[Errno 22] Invalid argument: '/Library/WebServer/ 
 Documents/duraseal/Comps/index.psd'' raised of class  
 'exceptions.IOError':
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/robust.py, line 32, in  
 check_common_error
try: return function(*args)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/rpath.py, line 1149, in append
return self.__class__(self.conn, self.base, self.index + (ext,))
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/rpath.py, line 884, in __init__
else: self.setdata()
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/rpath.py, line 909, in setdata
if self.lstat(): self.conn.rpath.setdata_local(self)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/rpath.py, line 1496, in  
 setdata_local
if Globals.eas_conn: rpath.data['ea'] = ea_get(rpath)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/eas_acls.py, line 589, in  
 rpath_ea_get
ea.read_from_rp(rp)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
 python2.3/site-packages/rdiff_backup/eas_acls.py, line 60, in  
 read_from_rp
attr_list = rp.conn.xattr.listxattr(rp.path, rp.issym())
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
 ppc.egg/xattr/__init__.py, line 178, in listxattr
return tuple(xattr(f).list(options=symlink and XATTR_NOFOLLOW or  
 0))
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
 ppc.egg/xattr/__init__.py, line 99, in list
res = self._list(options | self.options).split('\x00')
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
 ppc.egg/xattr/__init__.py, line 16, in _func
return func(first, *args)

 Exception '[Errno 22] Invalid 

[rdiff-backup-users] error 22 -- rdiff-backup 1.2.5 OS X

[sphen boyle]

hi there..

just installed rdiff-backup on a couple machines (one on server 10.5.6  
python 2.5.1 and  one on server 10.4.11 python 2.3)  -- everything  
worked fine upon first backup - but is throwing some errors on 4 files  
upon subsequent ones.  nothing too crazy with the setup that i am  
aware of. the command i am running is as follows:


rdiff-backup -v5 --remote-schema 'ssh -c arcfour -C %s  rdiff-backup   
--server' --print-statistics /Library/WebServer r...@192.168.254.244::/ 
Volumes/Storage/rdiff/WebServer


the following is what is put out to the logfile.  other files do seem  
to increment fine - but ive only ran the backup a few times...  please  
let me know if there is any more information that i can give to narrow  
this down.  thanks!


Using rdiff-backup version 1.2.5
Executing ssh -C r...@192.168.254.244 rdiff-backup --server
No increments older than Sat Nov 15 16:34:31 2008 found, exiting.
Using rdiff-backup version 1.2.5
Executing ssh -c arcfour -C r...@192.168.254.244  rdiff-backup  --server
Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Library/WebServer
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Library/WebServer
escape_dos_devices not required by filesystem at /Library/WebServer
Starting increment operation /Library/WebServer to /Volumes/Storage/ 
rdiff/WebServer
Exception '[Errno 22] Invalid argument: '/Library/WebServer/Documents/ 
duraseal/Comps/index.psd'' raised of class 'exceptions.IOError':
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/robust.py, line 32, in  
check_common_error

try: return function(*args)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1149, in append

return self.__class__(self.conn, self.base, self.index + (ext,))
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 884, in __init__

else: self.setdata()
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 909, in setdata

if self.lstat(): self.conn.rpath.setdata_local(self)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1496, in  
setdata_local

if Globals.eas_conn: rpath.data['ea'] = ea_get(rpath)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 589, in  
rpath_ea_get

ea.read_from_rp(rp)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 60, in  
read_from_rp

attr_list = rp.conn.xattr.listxattr(rp.path, rp.issym())
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 178, in listxattr
return tuple(xattr(f).list(options=symlink and XATTR_NOFOLLOW or  
0))
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 99, in list

res = self._list(options | self.options).split('\x00')
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 16, in _func

return func(first, *args)

Exception '[Errno 22] Invalid argument: '/Library/WebServer/Documents/ 
duraseal/Comps/inside.psd'' raised of class 'exceptions.IOError':
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/robust.py, line 32, in  
check_common_error

try: return function(*args)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1149, in append

return self.__class__(self.conn, self.base, self.index + (ext,))
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 884, in __init__

else: self.setdata()
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 909, in setdata

if self.lstat(): self.conn.rpath.setdata_local(self)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1496, in  
setdata_local

if Globals.eas_conn: rpath.data['ea'] = ea_get(rpath)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 589, in  
rpath_ea_get

ea.read_from_rp(rp)
  File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 60, in  
read_from_rp

attr_list = rp.conn.xattr.listxattr(rp.path, rp.issym())
  File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 178, in 

Re: [rdiff-backup-users] error 22 -- rdiff-backup 1.2.5 OS X

[Andrew Ferguson]

Hi Sphen,

Strange error ... Each time, it comes when rdiff-backup is asking for  
a list of the extended attributes on those 4 files.


What does `file` and `ls -...@e` report on each of those files?

/Library/WebServer/Documents/duraseal/Comps/index.psd
/Library/WebServer/Documents/duraseal/Comps/inside.psd
/Library/WebServer/Documents/duraseal/Comps/landing.psd
/Library/WebServer/Documents/duraseal/RequestADemo.html


And, just to confirm, this is on the 10.4.11 server, yes? I wonder  
what would happen if you copy those files to the 10.5.6 server and try  
again...



thanks,
Andrew


On Jan 14, 2009, at 7:10 PM, sphen boyle wrote:


hi there..

just installed rdiff-backup on a couple machines (one on server  
10.5.6 python 2.5.1 and  one on server 10.4.11 python 2.3)  --  
everything worked fine upon first backup - but is throwing some  
errors on 4 files upon subsequent ones.  nothing too crazy with the  
setup that i am aware of. the command i am running is as follows:


rdiff-backup -v5 --remote-schema 'ssh -c arcfour -C %s  rdiff- 
backup  --server' --print-statistics /Library/WebServer r...@192.168.254.244 
::/Volumes/Storage/rdiff/WebServer


the following is what is put out to the logfile.  other files do  
seem to increment fine - but ive only ran the backup a few times...   
please let me know if there is any more information that i can give  
to narrow this down.  thanks!


Using rdiff-backup version 1.2.5
Executing ssh -C r...@192.168.254.244 rdiff-backup --server
No increments older than Sat Nov 15 16:34:31 2008 found, exiting.
Using rdiff-backup version 1.2.5
Executing ssh -c arcfour -C r...@192.168.254.244  rdiff-backup  -- 
server

Unable to import module posix1e from pylibacl package.
POSIX ACLs not supported on filesystem at /Library/WebServer
Unable to import win32security module. Windows ACLs
not supported by filesystem at /Library/WebServer
escape_dos_devices not required by filesystem at /Library/WebServer
Starting increment operation /Library/WebServer to /Volumes/Storage/ 
rdiff/WebServer
Exception '[Errno 22] Invalid argument: '/Library/WebServer/ 
Documents/duraseal/Comps/index.psd'' raised of class  
'exceptions.IOError':
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/robust.py, line 32, in  
check_common_error

   try: return function(*args)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1149, in append

   return self.__class__(self.conn, self.base, self.index + (ext,))
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 884, in __init__

   else: self.setdata()
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 909, in setdata

   if self.lstat(): self.conn.rpath.setdata_local(self)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1496, in  
setdata_local

   if Globals.eas_conn: rpath.data['ea'] = ea_get(rpath)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 589, in  
rpath_ea_get

   ea.read_from_rp(rp)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/eas_acls.py, line 60, in  
read_from_rp

   attr_list = rp.conn.xattr.listxattr(rp.path, rp.issym())
 File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 178, in listxattr
   return tuple(xattr(f).list(options=symlink and XATTR_NOFOLLOW or  
0))
 File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 99, in list

   res = self._list(options | self.options).split('\x00')
 File /Library/Python/2.3/site-packages/xattr-0.4-py2.3-macosx-10.4- 
ppc.egg/xattr/__init__.py, line 16, in _func

   return func(first, *args)

Exception '[Errno 22] Invalid argument: '/Library/WebServer/ 
Documents/duraseal/Comps/inside.psd'' raised of class  
'exceptions.IOError':
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/robust.py, line 32, in  
check_common_error

   try: return function(*args)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 1149, in append

   return self.__class__(self.conn, self.base, self.index + (ext,))
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 884, in __init__

   else: self.setdata()
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/rdiff_backup/rpath.py, line 909, in setdata

   if self.lstat(): self.conn.rpath.setdata_local(self)
 File /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 

Re: [rdiff-backup-users] Error on remote restore (1.2.3)

[Dominic]

Andrew Ferguson wrote:

  
  On Jan 5, 2009, at 6:06 AM, Dominic wrote:
  
  
 ... but I do get an error
with rdiff-backup 1.2.4 when running from a *Windows* client (to
Linux-based rdiff-backup server) thus:
C:\rdiff-backup -r 0D dominic-pcchi...@192.168.100.125::archives/mydocs/myfile.docx myfile.docx


  
  
I will release 1.2.5 shortly so that we see better error messages.
After that, feel free to try again, and we can see what went wrong.
Hi Andrew

When I run it with 1.2.5 I get the error message below, I hope this
helps you some more (note that despite the message, the file
'archives/mydocs/meetings.docx' does exist in the archive).

Dominic
C:\rdiff-backup -r 0D dominic-pcchi...@192.168.100.125:
:archives/mydocs/meetings.docx meetings.docx
Exception '[Error 2] The system cannot find the file specified' raised of class
'type 'exceptions.WindowsError'':
  File "rdiff_backup\Main.pyc", line 304, in error_check_Main
  File "rdiff_backup\Main.pyc", line 321, in Main
  File "rdiff_backup\SetConnections.pyc", line 76, in cmdpair2rp
  File "rdiff_backup\SetConnections.pyc", line 139, in init_connection
  File "subprocess.pyc", line 595, in __init__
  File "subprocess.pyc", line 821, in _execute_child

Traceback (most recent call last):
  File "rdiff-backup", line 30, in module
  File "rdiff_backup\Main.pyc", line 304, in error_check_Main
  File "rdiff_backup\Main.pyc", line 321, in Main
  File "rdiff_backup\SetConnections.pyc", line 76, in cmdpair2rp
  File "rdiff_backup\SetConnections.pyc", line 139, in init_connection
  File "subprocess.pyc", line 595, in __init__
  File "subprocess.pyc", line 821, in _execute_child
WindowsError: [Error 2] The system cannot find the file specified




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error on remote restore (1.2.3)

[Andrew Ferguson]

On Jan 5, 2009, at 6:06 AM, Dominic wrote:

... but I do get an error with rdiff-backup 1.2.4 when running from  
a *Windows* client (to Linux-based rdiff-backup server) thus:
C:\rdiff-backup -r 0D dominic-pcchi...@192.168.100.125::archives/ 
mydocs/myfile.docx myfile.docx

Traceback (most recent call last):
  File rdiff-backup, line 30, in module
  File rdiff_backup\Main.pyc, line 307, in error_check_Main
  File rdiff_backup\robust.pyc, line 77, in is_routine_fatal
NameError: global name 'e' is not defined
Is this the known bug with Windows escaping  (Savannah #25041) or  
something different? If it is, is the only solution to move to  
1.3.0? (Strangely the last line of my error messages is the same as  
Ryan reported in 1.3.0 ('long filename error' thread))


Hi Dominic,

Due to the typo in robust.py on line 77 (e.errno should be  
exc.errno) we don't know what error is causing your restore to fail.


I will release 1.2.5 shortly so that we see better error messages.  
After that, feel free to try again, and we can see what went wrong.




Andrew___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error on remote restore (1.2.3)

[Dominic]

... but I do get an error with rdiff-backup 1.2.4 when running from a
*Windows* client (to Linux-based rdiff-backup server) thus:
C:\rdiff-backup -r 0D dominic-pcchi...@192.168.100.125::archives/mydocs/myfile.docx myfile.docx
Traceback (most recent call last):
  File "rdiff-backup", line 30, in module
  File "rdiff_backup\Main.pyc", line 307, in error_check_Main
  File "rdiff_backup\robust.pyc", line 77, in is_routine_fatal
NameError: global name 'e' is not defined

Is this the known bug with Windows escaping (Savannah #25041) or
something different? If it is, is the only solution to move to 1.3.0?
(Strangely the last line of my error messages is the same as Ryan
reported in 1.3.0 ('long filename error' thread))

Dominic




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error on remote restore (1.2.3)

[Dominic]

Experimenting with restoring files I have hit an error and I hope 
someone can help me. Running on the local backup machine this restore 
works fine:


rdiff-backup -r 0D /home/dominic-pcchips2/archives/mydocs/To Do.xlsx 
~/To Do.xlsx


but when I try to restore by running from a remote Linux machine thus

rdiff-backup -r 0D dominic-pcchi...@192.168.100.125::archives/mydocs/To 
Do.xlsx ~/To Do.xlsx


I get errors (see below). I am using rdiff-backup 1.2.3 at both ends. Am 
I doing something wrong? To rule out the possibility of something being 
wrong on the remote machine I ran the same command on the backup machine 
i.e. looping back to itself - the same error messages occur.


Dominic
-
Exception '
Warning Security Violation!
Bad request for function: open
with arguments: ['archives/mydocs/rdiff-backup-data/test ', 'w']
' raised of class 'class 'rdiff_backup.Security.Violation'':
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
304, in error_check_Main

   try: Main(arglist)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
324, in Main

   take_action(rps)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
290, in take_action

   elif action == restore-as-of: Restore(rps[0], rps[1], 1)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
550, in Restore

   dest_rp.conn.fs_abilities.restore_set_globals(dest_rp)
 File /usr/lib/python2.5/site-packages/rdiff_backup/fs_abilities.py, 
line 955, in restore_set_globals

   rsg.set_must_escape_trailing_spaces(Globals.rbdir)
 File /usr/lib/python2.5/site-packages/rdiff_backup/fs_abilities.py, 
line 836, in set_must_escape_trailing_spaces

   space_rp.touch()
 File /usr/lib/python2.5/site-packages/rdiff_backup/rpath.py, line 
1027, in touch

   self.conn.open(self.path, w).close()
 File /usr/lib/python2.5/site-packages/rdiff_backup/connection.py, 
line 450, in __call__

   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.5/site-packages/rdiff_backup/connection.py, 
line 370, in reval

   if isinstance(result, Exception): raise result

Traceback (most recent call last):
 File /usr/bin/rdiff-backup, line 30, in module
   rdiff_backup.Main.error_check_Main(sys.argv[1:])
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
304, in error_check_Main

   try: Main(arglist)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
324, in Main

   take_action(rps)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
290, in take_action

   elif action == restore-as-of: Restore(rps[0], rps[1], 1)
 File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 
550, in Restore

   dest_rp.conn.fs_abilities.restore_set_globals(dest_rp)
 File /usr/lib/python2.5/site-packages/rdiff_backup/fs_abilities.py, 
line 955, in restore_set_globals

   rsg.set_must_escape_trailing_spaces(Globals.rbdir)
 File /usr/lib/python2.5/site-packages/rdiff_backup/fs_abilities.py, 
line 836, in set_must_escape_trailing_spaces

   space_rp.touch()
 File /usr/lib/python2.5/site-packages/rdiff_backup/rpath.py, line 
1027, in touch

   self.conn.open(self.path, w).close()
 File /usr/lib/python2.5/site-packages/rdiff_backup/connection.py, 
line 450, in __call__

   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.5/site-packages/rdiff_backup/connection.py, 
line 370, in reval

   if isinstance(result, Exception): raise result
rdiff_backup.Security.Violation:
Warning Security Violation!
Bad request for function: open
with arguments: ['archives/mydocs/rdiff-backup-data/test ', 'w']

Fatal Error: Lost connection to the remote system




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error on remote restore (1.2.3)

[Dominic]

wrote:

On Jan 1, 2009, at 5:58 AM, Dominic wrote:
Experimenting with restoring files I have hit an error and I hope 
someone can help me. Running on the local backup machine this restore 
works fine:


rdiff-backup -r 0D /home/dominic-pcchips2/archives/mydocs/To 
Do.xlsx ~/To Do.xlsx


but when I try to restore by running from a remote Linux machine thus

rdiff-backup -r 0D 
dominic-pcchi...@192.168.100.125::archives/mydocs/To Do.xlsx ~/To 
Do.xlsx


I get errors (see below). I am using rdiff-backup 1.2.3 at both ends. 
Am I doing something wrong? To rule out the possibility of something 
being wrong on the remote machine I ran the same command on the 
backup machine i.e. looping back to itself - the same error messages 
occur.



Oh, damn. :-(I'll spin 1.2.4 in just a moment to disable the new 
escape trailing spaces code. The fix for this might take awhile, since 
it also means that the escape dos devices code (2 years old) has 
become incorrect. Sorry for missing that during testing.


crummy way to start the new year,
Andrew
Thanks for fixing the error so quickly, I can confirm that this problem 
does not occur with 1.2.4


Dominic


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error in 1.2.1

[Gregory Oschwald]

I am experiencing the following error with 1.2.1.  Any thoughts on how to
fix it?

Previous backup seems to have failed, regressing destination now.
Exception 'RPath instance has no attribute 'inc_compressed'' raised of class
+'type 'exceptions.AttributeError'':
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 302,
in
+error_check_Main
try: Main(arglist)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 322,
in
+Main
take_action(rps)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 278,
in
+take_action
elif action == backup: Backup(rps[0], rps[1])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 335,
in
+Backup
backup_final_init(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 435,
in
+backup_final_init
checkdest_if_necessary(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 829,
in
+checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
448,
+in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
370,
+in reval
if isinstance(result, Exception): raise result

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 23, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 302,
in
+error_check_Main
try: Main(arglist)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 322,
in
+Main
take_action(rps)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 278,
in
+take_action
elif action == backup: Backup(rps[0], rps[1])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 335,
in
+Backup
backup_final_init(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 435,
in
+backup_final_init
checkdest_if_necessary(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 829,
in
+checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
448,
+in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
370,
+in reval
if isinstance(result, Exception): raise result
AttributeError: RPath instance has no attribute 'inc_compressed'
Fatal Error: Lost connection to the remote system
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error in 1.2.1

[Gregory Oschwald]

I am experiencing the following error with 1.2.1.  Any thoughts on how to
fix it?

Previous backup seems to have failed, regressing destination now.
Exception 'RPath instance has no attribute 'inc_compressed'' raised of class
+'type 'exceptions.AttributeError'':
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 302,
in
+error_check_Main
try: Main(arglist)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 322,
in
+Main
take_action(rps)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 278,
in
+take_action
elif action == backup: Backup(rps[0], rps[1])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 335,
in
+Backup
backup_final_init(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 435,
in
+backup_final_init
checkdest_if_necessary(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 829,
in
+checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
448,
+in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
370,
+in reval
if isinstance(result, Exception): raise result

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 23, in module
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 302,
in
+error_check_Main
try: Main(arglist)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 322,
in
+Main
take_action(rps)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 278,
in
+take_action
elif action == backup: Backup(rps[0], rps[1])
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 335,
in
+Backup
backup_final_init(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 435,
in
+backup_final_init
checkdest_if_necessary(rpout)
  File /var/lib/python-support/python2.5/rdiff_backup/Main.py, line 829,
in
+checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
448,
+in __call__
return apply(self.connection.reval, (self.name,) + args)
  File /var/lib/python-support/python2.5/rdiff_backup/connection.py, line
370,
+in reval
if isinstance(result, Exception): raise result
AttributeError: RPath instance has no attribute 'inc_compressed'
Fatal Error: Lost connection to the remote system
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error while restoring

[Madan Kumar]

Hi All,

I am very thankfull to you to provide me such support and guidence.
I am using rdiff-backup on windowsXP and on windows Vista using cygwin.

I can get the backups and restore it by running Cygwin.bat it is in C:\Cygwin\ 
folder. Or I can do the same by running bash.exe file it is in C:\Cygwin\bin\ 
folder. 
case1- By Running Cygwin.bat--
Suppose I need to get the backup of one folder(F:\Source) and I save the backup 
to G:\Dest folder. (No prob its happening) and the command is $rdiff-backup -b 
F:/Source G:/Dest.
Now If I restore it by running the command $rdiff-backup -r now G:/Dest 
F:/Source It gives me one error message Fatel Error- Could Not Find 
rdiff-backup repository at G:/Dest.
I am not able to understand why this error is occuring?
If I take the back up using the command- $rdiff-backup -b F:/Source Dest. Then 
this backup folder(Dest) automatically saved to C:\Cygwin\Home\Administrator 
folder. While restoring I run the command $rdiff-backup -r now Dest F:/Source. 
This time it is restoring successfully.

case 2- By Running bash.exe--
Problem is same but while taking the backups it stores to C:\Cygwin\bin folder.

Now my question is- Is it the limitation of rdiff-backup that you can take the 
backup only to the folders that I mention above?
If I want to take the backup of any folder to the destination specified by me, 
then how can I restore it form there?



Please give me some helpfull?




Thanks  Regards
M Chauhan
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error: command 'gcc' failed with exit status 1

[gart algar]

Hello,
Wilson Azevedo a écrit :
 Friends rdiff-backup's users

 I'm a Linux (Xandros Debian Etch, on an Asus EeePC) novice user and
 need help to upgrade rdiff-backup to version 1.1.6 or 1.1.7. The
 version 1.1.5 I've installed from debian.org repository has a bug in
 working with Samba mounted windows file systems as well as sshfs
 mounted remote folders -- where I need to place the backup copies from
 my EeePC.
I don't know how to help you with GCC not compiling the header file, but 
since you are new to linux, maybe you should try to install rdiff-backup 
from another repository. I'm not familliar with Xandros, so these may 
not be accurate or even not work.

You should edit your file /etc/apt/sources.list. Something like
sudo gedit /etc/apt/sources.list should work

add the following line :
deb http://www.backports.org/debian etch-backports main contrib non-free

Save and exit. Now, you can install rdiff-backup from this repository, 
like this :

apt-get -t etch-backports install rdiff-backup

I hope it will help you.



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error: command 'gcc' failed with exit status 1

[Wilson Azevedo]

`As 10:51 AM 2/27/2008, gart algar disse:

add the following line :
deb http://www.backports.org/debian etch-backports main contrib non-free


Gart,

Thank you very much. But when I've checked this repository I've found 
a 1.1.14 version -- older than 1.1.5 that I've installed from 
debian-etch repository.


Wilson



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error: command 'gcc' failed with exit status 1

[Wilson Azevedo]

Friends rdiff-backup's users

I'm a Linux (Xandros Debian Etch, on an Asus EeePC) novice user and
need help to upgrade rdiff-backup to version 1.1.6 or 1.1.7. The
version 1.1.5 I've installed from debian.org repository has a bug in
working with Samba mounted windows file systems as well as sshfs
mounted remote folders -- where I need to place the backup copies from
my EeePC.

I've downloaded the 1.1.6 package and seen that it is in fact a set of
scripts in Python. So I've followed the instructions from the README
file in order to install it and got an error message talking about a
program called gcc. I went to Synaptic and found gcc in Debian
repository, marked it for install and applyed. Then I've run again the
python setup.py install script and got the error messages below. What
should I do? Is there something else that need to be done before
installing rdiff-backup on my EeePC? As I told you, this EeePC is my
first linux computer and I'm still learning to use its basic features
and resources.

Thanks in advance for any help.

Wilson

--

 sudo python setup.py install
running install
running build
running build_py
running build_ext
building 'rdiff_backup.C' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/include/python2.4 -c cmodule.c -o 
build/temp.linux-i686-2.4/cmodule.o

cmodule.c:24:20: error: Python.h: No such file or directory
cmodule.c:25:23: error: sys/types.h: No such file or directory
cmodule.c:26:22: error: sys/stat.h: No such file or directory
cmodule.c:27:20: error: unistd.h: No such file or directory
cmodule.c:28:19: error: errno.h: No such file or directory
cmodule.c:72: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:73: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:74: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:75: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:76: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:80: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token
cmodule.c:82: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? 
before ?*? token

cmodule.c:83: error: expected identifier or ?(? before ?{? token
cmodule.c:207: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token
cmodule.c:209: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token

cmodule.c:210: error: expected identifier or ?(? before ?{? token
cmodule.c:223: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token
cmodule.c:225: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token

cmodule.c:226: error: expected identifier or ?(? before ?{? token
cmodule.c:234: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token
cmodule.c:236: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token

cmodule.c:237: error: expected identifier or ?(? before ?{? token
cmodule.c:258:19: error: stdio.h: No such file or directory
cmodule.c:259:20: error: stdlib.h: No such file or directory
cmodule.c:260:19: error: ctype.h: No such file or directory
cmodule.c:262: error: expected declaration specifiers or ?...? before ?size_t?
cmodule.c:262: error: expected declaration specifiers or ?...? before ?size_t?
cmodule.c: In function ?high_water_alloc?:
cmodule.c:270: error: ?bufsize? undeclared (first use in this function)
cmodule.c:270: error: (Each undeclared identifier is reported only once
cmodule.c:270: error: for each function it appears in.)
cmodule.c:270: error: ?newsize? undeclared (first use in this function)
cmodule.c:274: warning: implicit declaration of function ?realloc?
cmodule.c:274: warning: assignment makes pointer from integer without a cast
cmodule.c: In function ?quote?:
cmodule.c:286: error: ?NULL? undeclared (first use in this function)
cmodule.c:287: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?quoted_str_len?

cmodule.c:287: error: ?quoted_str_len? undeclared (first use in this function)
cmodule.c:290: error: ?size_t? undeclared (first use in this function)
cmodule.c:290: error: expected ?;? before ?nonpr?
cmodule.c:295: error: ?nonpr? undeclared (first use in this function)
cmodule.c:295: warning: left-hand operand of comma expression has no effect
cmodule.c:295: error: ?total_len? undeclared (first use in this function)
cmodule.c:295: warning: value computed is not used
cmodule.c:297: warning: implicit declaration of function ?isprint?
cmodule.c:297: warning: implicit declaration of function ?isspace?
cmodule.c:304: error: too many arguments to function ?high_water_alloc?
cmodule.c: At top level:
cmodule.c:354: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token
cmodule.c:363: error: expected ?=?, ?,?, ?;?, ?asm? or 
?__attribute__? before ?*? token
cmodule.c:406: error: expected ?=?, ?,?, ?;?, 

Re: [rdiff-backup-users] error in long running system

[Andrew Ferguson]

Iain Dooley wrote:
 hi all, i've been running rdiff-backup for about a year and a half with no 
 troubles. i use version 1.1.5 on freebsd 6.2R.
 
 yesterday on two of my systems, i got the error below. other systems are 
 still running correctly.

 socata# /root/backup.sh
File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
 810, in checkdest_need_check
  if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs)
File 
 /usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
 448, in __call__
  return apply(self.connection.reval, (self.name,) + args)
File 
 /usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
 367, in reval
  for arg in args: self._put(arg, req_num)
File 
 /usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
 139, in _put
  else: self._putobj(obj, req_num)
File 
 /usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
 144, in _putobj
  self._write(o, pickle.dumps(obj, 1), req_num)
File /usr/local/lib/python2.4/pickle.py, line 1386, in dumps
  Pickler(file, protocol, bin).dump(obj)
File /usr/local/lib/python2.4/pickle.py, line 231, in dump
  self.save(obj)
File /usr/local/lib/python2.4/pickle.py, line 293, in save
  f(self, obj) # Call unbound method with explicit self
File /usr/local/lib/python2.4/pickle.py, line 614, in save_list
  self._batch_appends(iter(obj))
File /usr/local/lib/python2.4/pickle.py, line 647, in _batch_appends
  save(x)
File /usr/local/lib/python2.4/pickle.py, line 293, in save
  f(self, obj) # Call unbound method with explicit self
File /usr/local/lib/python2.4/pickle.py, line 737, in save_inst
  stuff = getstate()
File /usr/local/lib/python2.4/site-packages/rdiff_backup/rpath.py, 
 line 754, in __getstate__
  assert self.conn is Globals.local_connection


Iain,

The bug you are seeing was fixed in version 1.1.12. Unfortunately, the
bug was in the rdiff-backup network protocol, which required that I
break the protocol in 1.1.12 in order to fix it.

Since you are using rdiff-backup on several computers, you would need to
upgrade rdiff-backup to version 1.1.14 on ALL of your computers if you
wanted to use the fixed version on one of them.

HOWEVER, there is a workaround: You can add the --force option to
rdiff-backup, and it will skip the code pathway that leads to this bug.



Best,
Andrew


-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error in long running system

[Iain Dooley]

hi all, i've been running rdiff-backup for about a year and a half with no 
troubles. i use version 1.1.5 on freebsd 6.2R.


yesterday on two of my systems, i got the error below. other systems are 
still running correctly.


i can't find anything meaningful in the messages below, does anyone else 
have any clues? i've checked and keychain/ssh connection is still working 
fine on both systems into the backup server.


cheers

iain

socata# /root/backup.sh
Exception '' raised of class 'exceptions.AssertionError':
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
295, in error_check_Main

try: Main(arglist)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
315, in Main

take_action(rps)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
271, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
328, in Backup

backup_final_init(rpout)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
425, in backup_final_init

checkdest_if_necessary(rpout)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
820, in checkdest_if_necessary

need_check = checkdest_need_check(dest_rp)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
810, in checkdest_need_check

if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
448, in __call__

return apply(self.connection.reval, (self.name,) + args)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
367, in reval

for arg in args: self._put(arg, req_num)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
139, in _put

else: self._putobj(obj, req_num)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
144, in _putobj

self._write(o, pickle.dumps(obj, 1), req_num)
  File /usr/local/lib/python2.4/pickle.py, line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
  File /usr/local/lib/python2.4/pickle.py, line 231, in dump
self.save(obj)
  File /usr/local/lib/python2.4/pickle.py, line 293, in save
f(self, obj) # Call unbound method with explicit self
  File /usr/local/lib/python2.4/pickle.py, line 614, in save_list
self._batch_appends(iter(obj))
  File /usr/local/lib/python2.4/pickle.py, line 647, in _batch_appends
save(x)
  File /usr/local/lib/python2.4/pickle.py, line 293, in save
f(self, obj) # Call unbound method with explicit self
  File /usr/local/lib/python2.4/pickle.py, line 737, in save_inst
stuff = getstate()
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/rpath.py, 
line 754, in __getstate__

assert self.conn is Globals.local_connection

Traceback (most recent call last):
  File /usr/local/bin/rdiff-backup, line 23, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
295, in error_check_Main

try: Main(arglist)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
315, in Main

take_action(rps)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
271, in take_action

elif action == backup: Backup(rps[0], rps[1])
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
328, in Backup

backup_final_init(rpout)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
425, in backup_final_init

checkdest_if_necessary(rpout)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
820, in checkdest_if_necessary

need_check = checkdest_need_check(dest_rp)
  File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 
810, in checkdest_need_check

if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
448, in __call__

return apply(self.connection.reval, (self.name,) + args)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
367, in reval

for arg in args: self._put(arg, req_num)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
139, in _put

else: self._putobj(obj, req_num)
  File 
/usr/local/lib/python2.4/site-packages/rdiff_backup/connection.py, line 
144, in _putobj

self._write(o, pickle.dumps(obj, 1), req_num)
  File /usr/local/lib/python2.4/pickle.py, line 1386, in dumps
Pickler(file, protocol, bin).dump(obj)
  File /usr/local/lib/python2.4/pickle.py, line 231, in dump
self.save(obj)
  File /usr/local/lib/python2.4/pickle.py, line 293, in save
f(self, obj) # Call unbound method with explicit self
  File /usr/local/lib/python2.4/pickle.py, line 614, in save_list
self._batch_appends(iter(obj))
  File 

Re: [rdiff-backup-users] Error in

[Andrew Ferguson]

Mario Doering wrote:
 Regressing file scripts/AddrDat.dll Exception '[Errno 22] Invalid
 argument' raised of class 'exceptions.OSError': File
 /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 302, in
 error_check_Main try: Main(arglist) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 322, in
 Main take_action(rps) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 280, in
 take_action elif action == check-destination-dir: CheckDest(rps[0])
 File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
 787, in CheckDest dest_rp.conn.regress.Regress(dest_rp) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 71,
 in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath):
 ITR(rf.index, rf) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/rorpiter.py, line
 281, in __call__ last_branch.fast_process(*args) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 267,
 in fast_process if rf.metadata_rorp.isreg():
 self.restore_orig_regfile(rf) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 297,
 in restore_orig_regfile rf.mirror_rp.get_parent_rp().fsync() # require
 move before inc delete File
 /usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1157,
 in fsync if not fp: self.conn.rpath.RPath.fsync_local(self) File
 /usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1170,
 in fsync_local os.fsync(fd)


You know, I think this bug has just been fixed in CVS. From this
traceback, it looks like it is the same as Savannah bug #21546

https://savannah.nongnu.org/bugs/?21546


which Marc Horowitz patched.


Andrew

--
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error with File name too long

[Philippe Froidevaux]

Hello,

I get an error with File name too long. I can correct it on the source
by removing the too-long file, but the destination still give me an
error (see attached files below) and rdiff-backup crashs.

How can I remove this error ?

system infos :
nas03:~# rdiff-backup --version
rdiff-backup 1.1.11
nas03:~# uname -a
SunOS diufnas03 5.10 Generic_118855-33 i86pc i386 i86pc
nas03:~# python --version
Python 2.5.1

filesystem source is NFS, target is ZFS.



Second (optional) question, is there a way to ignore the file system
error on rdiff-backup ?



Thanks !

Philippe.

-- 
Meilleures salutations / Mit freundlichen Gruessen / Kind regards
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Philippe Froidevaux  [EMAIL PROTECTED]
Départment of Computer ScienceSystems Manager
Boulevard de Pérolles 90tel: +41 26 300 83 42
CH-1700 Fribourgfax: +41 26 300 96 42
http://diuf.unifr.ch/techsupport/




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error with File name too long

[Philippe Froidevaux]

[same message but with the attachement now :) sorry]


Hello,

I get an error with File name too long. I can correct it on the source
by removing the too-long file, but the destination still give me an
error (see attached files below) and rdiff-backup crashs.

How can I remove this error ?

system infos :
nas03:~# rdiff-backup --version
rdiff-backup 1.1.11
nas03:~# uname -a
SunOS diufnas03 5.10 Generic_118855-33 i86pc i386 i86pc
nas03:~# python --version
Python 2.5.1

filesystem source is NFS, target is ZFS.



Second (optional) question, is there a way to ignore the file system
error on rdiff-backup ?



Thanks !

Philippe.

-- 
Meilleures salutations / Mit freundlichen Gruessen / Kind regards
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Philippe Froidevaux  [EMAIL PROTECTED]
Départment of Computer ScienceSystems Manager
Boulevard de Pérolles 90tel: +41 26 300 83 42
CH-1700 Fribourgfax: +41 26 300 96 42
http://diuf.unifr.ch/techsupport/



Previous backup seems to have failed, regressing destination now.
Exception '[Errno 78] File name too long: 
'/export/backup_home/diufnas01.vol05/rdiff-backup-data/home/hannania/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes/.themes''
 raised of class 'type 'exceptions.OSError'':
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 299, 
in error_check_Main
try: Main(arglist)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 319, 
in Main
take_action(rps)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 275, 
in take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 332, 
in Backup
backup_final_init(rpout)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 432, 
in backup_final_init
checkdest_if_necessary(rpout)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py, line 831, 
in checkdest_if_necessary
dest_rp.conn.regress.Regress(dest_rp)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
71, in Regress
for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf)
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
196, in iterate_meta_rfs
for raw_rf, metadata_rorp in collated:
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/rorpiter.py, line 
92, in Collate2Iters
try: relem1 = riter1.next()
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 
174, in helper
for sub_sub_rf in helper(sub_rf):
  File /usr/local/lib/python2.5/site-packages/rdiff_backup/regress.py, line 

[rdiff-backup-users] Error in

[Mario Doering]

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 supported by
filesystem at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data
Directories on file system
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
are not fsyncable. Assuming it's unnecessary. Unable to import module
xattr. Extended attributes not supported on filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package. ACLs not
supported on filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
escape_dos_devices not required by filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
-
Detected abilities
for /mnt/backup_local/daehne/Inetpub/rdiff-backup-data (read/write)
file system: Ownership changing   Off Hard
linking Off fsync()
directories  Off Directory inc
permissionsOff High-bit
permissions On Symlink
permissions  Off Extended
filenames   Off Access control
lists Off Extended
attributes  Off Case
sensitivity On Escape DOS
devices   Off Mac OS X style resource
forksOff Mac OS X Finder information
Off -
Restore: must_escape_dos_devices = 0 Regressing to Wed Sep  5 01:10:03
2007 Regressing attributes of /mnt/backup_local/daehne/Inetpub/ASP
Regressing attributes of /mnt/backup_local/daehne/Inetpub/AdminScripts
Regressing attributes
of /mnt/backup_local/daehne/Inetpub/ftproot/daehne/datenbank Regressing
attributes of /mnt/backup_local/daehne/Inetpub/ftproot/daehne
Regressing attributes of /mnt/backup_local/daehne/Inetpub/ftproot
Regressing file scripts/AddrDat.dll Exception '[Errno 22] Invalid
argument' raised of class 'exceptions.OSError': File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 302, in
error_check_Main try: Main(arglist) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 322, in
Main take_action(rps) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 280, in
take_action elif action == check-destination-dir: CheckDest(rps[0])
File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
787, in CheckDest dest_rp.conn.regress.Regress(dest_rp) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 71,
in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath):
ITR(rf.index, rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/rorpiter.py, line
281, in __call__ last_branch.fast_process(*args) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 267,
in fast_process if rf.metadata_rorp.isreg():
self.restore_orig_regfile(rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 297,
in restore_orig_regfile rf.mirror_rp.get_parent_rp().fsync() # require
move before inc delete File
/usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1157,
in fsync if not fp: self.conn.rpath.RPath.fsync_local(self) File
/usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1170,
in fsync_local os.fsync(fd)

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 23, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
302, in error_check_Main try: Main(arglist)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
322, in Main take_action(rps)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
280, in take_action elif action == check-destination-dir:
CheckDest(rps[0]) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 787, in
CheckDest dest_rp.conn.regress.Regress(dest_rp) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 71,
in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath):
ITR(rf.index, rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/rorpiter.py, line
281, in __call__ last_branch.fast_process(*args) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 267,
in fast_process if rf.metadata_rorp.isreg():
self.restore_orig_regfile(rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 297,
in restore_orig_regfile rf.mirror_rp.get_parent_rp().fsync() # require
move before inc delete File
/usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1157,
in fsync if not fp: self.conn.rpath.RPath.fsync_local(self) File

Re: [rdiff-backup-users] Error in

[David]

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 destination.

rdiff-backup wants to preserve the permissions of the source perfectly
at the destination (so it can compare against them in the future), but
a cifs mount doesn't provide the ability to create hardlinks,
symlinks, set extended attributes, etc. Just basic stuff like modified
date basic ACLS/permissions+mods.

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 etc it wants to on your backup destination.

Preferably log into the remote server, and run rdiff-backup locally.

Alternately, you may be able to run rdiff-backup --check over a nfs
mountpoint, or against a rdiff-backup service runnning on the remote
host.

It may be another reason (I'm not familiar with rdiff-backup's
internals and stack trace), but first try the above, then post the
error if you get one.

David


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Mario Doering]

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 etc it wants to on your backup destination.
 
 Preferably log into the remote server, and run rdiff-backup locally.
 
 Alternately, you may be able to run rdiff-backup --check over a nfs
 mountpoint, or against a rdiff-backup service runnning on the remote
 host.

The check command results in the same error as the
check-destination-dir.

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 :)


# rdiff-backup -v 5 --check /mnt/backup_local/daehne/Inetpub

Using rdiff-backup version 1.1.14
Warning: hard linking not supported by filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data Directories on
file system
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
are not fsyncable. Assuming it's unnecessary. Unable to import module
xattr. Extended attributes not supported on filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
Unable to import module posix1e from pylibacl package. ACLs not
supported on filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
escape_dos_devices not required by filesystem
at /mnt/backup_local/daehne/Inetpub/rdiff-backup-data/rdiff-backup.tmp.0
-
Detected abilities
for /mnt/backup_local/daehne/Inetpub/rdiff-backup-data (read/write)
file system: Ownership changing   Off Hard
linking Off fsync()
directories  Off Directory inc
permissionsOff High-bit
permissions On Symlink
permissions  Off Extended
filenames   Off Access control
lists Off Extended
attributes  Off Case
sensitivity On Escape DOS
devices   Off Mac OS X style resource
forksOff Mac OS X Finder information
Off -
Restore: must_escape_dos_devices = 0 Regressing to Wed Sep  5 01:10:03
2007 Regressing attributes of /mnt/backup_local/daehne/Inetpub/ASP
Regressing attributes of /mnt/backup_local/daehne/Inetpub/AdminScripts
Regressing attributes
of /mnt/backup_local/daehne/Inetpub/ftproot/daehne/datenbank Regressing
attributes of /mnt/backup_local/daehne/Inetpub/ftproot/daehne
Regressing attributes of /mnt/backup_local/daehne/Inetpub/ftproot
Regressing file scripts/AddrDat.dll Exception '[Errno 22] Invalid
argument' raised of class 'exceptions.OSError': File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 302, in
error_check_Main try: Main(arglist) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 322, in
Main take_action(rps) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 280, in
take_action elif action == check-destination-dir: CheckDest(rps[0])
File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
787, in CheckDest dest_rp.conn.regress.Regress(dest_rp) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 71,
in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath):
ITR(rf.index, rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/rorpiter.py, line
281, in __call__ last_branch.fast_process(*args) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 267,
in fast_process if rf.metadata_rorp.isreg():
self.restore_orig_regfile(rf) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 297,
in restore_orig_regfile rf.mirror_rp.get_parent_rp().fsync() # require
move before inc delete File
/usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1157,
in fsync if not fp: self.conn.rpath.RPath.fsync_local(self) File
/usr/lib64/python2.4/site-packages/rdiff_backup/rpath.py, line 1170,
in fsync_local os.fsync(fd)

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 23, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
302, in error_check_Main try: Main(arglist)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
322, in Main take_action(rps)
  File /usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line
280, in take_action elif action == check-destination-dir:
CheckDest(rps[0]) File
/usr/lib64/python2.4/site-packages/rdiff_backup/Main.py, line 787, in
CheckDest dest_rp.conn.regress.Regress(dest_rp) File
/usr/lib64/python2.4/site-packages/rdiff_backup/regress.py, line 71,
in Regress 

Re: [rdiff-backup-users] Error in

[David]

 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 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 is now running against the same files as in your original
post, but it is now able to set extended attributes, create hardlinks
etc, because it has direct access to the ext3 filesystem, rather than
going through the limited virtual filesystem under the cifs
mountpoint.

I cannot install nfs on that machine,
 but I can rsync all the stuff to another directory (ext3) and run the
 check command there.


That should work also. But it won't fix the warnings (inability to do
xattrs etc) you'll still be getting by trying to run rdiff-backup onto
a cifs mount.

I have another question: Was your rdiff-backup to a cifs mount working
before? It's possible that rdiff-backup works fine to a cifs (with
warnings about fs limitations), but the regressing doesn't. There's a
fair chance that the regressing logic isn't as well tested as the main
backup logic. In which case you will need to remember to ssh into the
remote server to fix rdiff-backup problems.

My suggestion is that you change your setup into a pull rather than
a push. ie install rdiff-backup on the remote host (backup server I
presume) and run it there instead.

If you can't do that, then (since rsync is installed on the remote
host), try running rdiff-backup to a local directory (if you have
space for it. You can play tricks with rsync and hardlinks if space is
an issue), then rsync (with appropriate options) your rdiff-backup
data over to the remote server for backup purposes. Preferably bypass
the cifs mountpoint entirely, rsync will do a better job of preserving
permssions, ownerships etc. But rsyncing to the cifs share should work
also. However you do it, check that you are able to restore from the
remote backup (including earlier snapshots).


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Mario Doering]

 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 do with cifs only.


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Mario Doering]

 
  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 is now running against the same files as in your original
 post, but it is now able to set extended attributes, create hardlinks
 etc, because it has direct access to the ext3 filesystem, rather than
 going through the limited virtual filesystem under the cifs
 mountpoint.

You mean locally on the computer which contains the backup-up files
(including riff-backup-data) shared via samba?

If yes, a login there is not possible. It is a terastation (=black
box) with only access via cifs.

And this share is mounted on the linux system running rdiff-backup
(which I meant with locally, cause the data it wants to back up is on a
remote host :) )


 I cannot install nfs on that machine,
  but I can rsync all the stuff to another directory (ext3) and run
  the check command there.
 
 
 That should work also. But it won't fix the warnings (inability to do
 xattrs etc) you'll still be getting by trying to run rdiff-backup onto
 a cifs mount.
 
 I have another question: Was your rdiff-backup to a cifs mount working
 before? It's possible that rdiff-backup works fine to a cifs (with
 warnings about fs limitations), but the regressing doesn't. There's a
 fair chance that the regressing logic isn't as well tested as the main
 backup logic. In which case you will need to remember to ssh into the
 remote server to fix rdiff-backup problems.


Ah yes.. I should have give more information on that.
The backups themselves work great. I guess that a backup session got
canceled in between .. maybe because of a network error or a reboot.

So it seems to me as well, that only the regression code is missing some
of the backup-cifs-features :)


@rdiff-backup crew:
Is this info enough for the coders to know where the problem is located?


 My suggestion is that you change your setup into a pull rather than
 a push. ie install rdiff-backup on the remote host (backup server I
 presume) and run it there instead.


It is set up that way, as written above :)



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Andrew Ferguson]

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]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[David]

 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


 And this share is mounted on the linux system running rdiff-backup
 (which I meant with locally, cause the data it wants to back up is on a
 remote host :) )

So, if I understand you correctly, you're backing up from one network
mount point to another? rdiff-backup pulls from source box, and your
mount point pushes it over the network to the terastation. That's
the kind of push I meant.

Graphically:

[source box] - [your box, running rdiff-backup] - [terastation with
cifs share]
 It is set up that way, as written above :)

You may be able to fix your current problem by running the regression
locally (after an rsync), then rsync your updated rdiff-backup
destination over to the cifs share (move the broken destination
somewhere else first, then remove it later if your new backup dest
works).


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Mario Doering]

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 server publishing the windows share is not known :-/



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error in

[Mario Doering]

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
  (which I meant with locally, cause the data it wants to back up is
  on a remote host :) )
 
 So, if I understand you correctly, you're backing up from one network
 mount point to another? rdiff-backup pulls from source box, and your
 mount point pushes it over the network to the terastation. That's
 the kind of push I meant.
 
 Graphically:
 
 [source box] - [your box, running rdiff-backup] - [terastation with
 cifs share]


It's even a bit more complicated here ;)

[a few windows servers] - [mounted at linux box] - internet - [linux
box running rdiff pulling the files] - [terastation with cifs share]

%)

hihi.. and beside these minor problems it works (so far) :D



 
 You may be able to fix your current problem by running the regression
 locally (after an rsync), then rsync your updated rdiff-backup
 destination over to the cifs share (move the broken destination
 somewhere else first, then remove it later if your new backup dest
 works).


Yes, that is a good workaround until a bugfix is available! At least as
long as there is enough space left :)



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error with accented character

[Andrew Ferguson]

SOULfly_B wrote:
 It seems this issue is not fixed cause I still have the problem.
 
 Attached is an extract of the traceback.

Hi Bruno,

You have picked up a very interesting bug, which was introduced in
1.1.8. When you first sent your report, I had only looked at the changes
I had made.

For the curious, it comes from this change:
http://cvs.savannah.gnu.org/viewvc/rdiff-backup/rdiff_backup/fs_abilities.py?root=rdiff-backupr1=1.30r2=1.31
and this email:
http://lists.nongnu.org/archive/html/rdiff-backup-users/2007-01/msg00096.html

What that change did was skewer the extended_filenames test.

From what I gather, Marc noticed that characters in the range 128-255
are valid on FAT32 and were being escaped by rdiff-backup, so he changed
the regex.

However, the regex was right for some situations, and it was what made
rdiff-backup work for you, Bruno.

The reason rdiff-backup was escaping valid characters in Marc's setup
was because the extended_filenames test was too general. It attempts to
create a file named : \ 0xE1 0x84 0x89 (without the spaces). The test
failed for Marc because : and \ are illegal in FAT32 filenames. It fails
for you because the Unicode characters are illegal in your SMB setup.

The regex we just talked about was redesigned to deal with the : and \,
and ignored the fact that the test can fail because of the Unicode
characters.

I don't have a fix for you yet since it will take some time to split out
the code and remove this bug properly. But stay tuned, and rest assured
that it will not be there in 1.1.15 and 1.2.0. :-)

Thank you so much,
Andrew

-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error with accented character

[Andrew Ferguson]

Bruno Spyckerelle wrote:
 I've updated rdiff-backup from 1.1.7 to 1.1.12 and i've now a bug with a 
 directory containing an accented letter.
 
 The backup is done using a samba share mounted with the following command :
 smbmount //IP/dir /home/$DIR -o username=admin,rw

Hi Bruno,

This bug is due to an accented character not being escaped properly. I
believe I fixed it in CVS a few days ago.

Dean, perhaps its time to spin 1.1.13?

Thanks,
Andrew

-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error on mounted CIFS Windows share

[Vytautas Stankevičius]

This bug was fixed in CVS and will be part of next release: 1.1.13



If you want to fix it now, add 'EOPNOTSUPP' to the list of error codes
that starts around line 54 in robust.py. It's a big list in the function
catch_error(exc) ... you can't miss it


Thanks. Now it proceeds further and finishes backup :)

-
Processing changed file visiems
Exception '[Errno 95] Operation not supported' raised of class 
'exceptions.OSError':
 File /var/lib/python-support/python2.4/rdiff_backup/robust.py, line 32, 
in check_common_error

   try: return function(*args)
 File /var/lib/python-support/python2.4/rdiff_backup/rpath.py, line 107, 
in copy

   rpout.symlink(rpin.readlink())
 File /var/lib/python-support/python2.4/rdiff_backup/rpath.py, line 890, 
in symlink

   self.conn.os.symlink(linktext, self.path)

SpecialFileError visiems [Errno 95] Operation not supported

...

Errors 1
-

Regards, Vytautas 




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error on mounted CIFS Windows share

[Andrew Ferguson]

Vytautas Stankevičius wrote:
 This bug was fixed in CVS and will be part of next release: 1.1.13
 
 If you want to fix it now, add 'EOPNOTSUPP' to the list of error codes
 that starts around line 54 in robust.py. It's a big list in the function
 catch_error(exc) ... you can't miss it
 
 Thanks. Now it proceeds further and finishes backup :)
 

 SpecialFileError visiems [Errno 95] Operation not supported

Great!

When you do the restore using rdiff-backup, it will recover the symlink
from its internal metadata (that's what the 'SpecialFileError' signifies).

Andrew

-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error: Too Many values to unpack

[Marcelo Diotto]

Yes, that was the problem.
Now i am with version 1.1.5 im both servers but i get this error:

Exception '' raised of class 'exceptions.AssertionError':
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 295, in
error_check_Main
   try: Main(arglist)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 315, in
Main
   take_action(rps)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 271, in
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 328, in
Backup
   backup_final_init(rpout)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 425, in
backup_final_init
   checkdest_if_necessary(rpout)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 820, in
checkdest_if_necessary
   need_check = checkdest_need_check(dest_rp)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 810, in
checkdest_need_check
   if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
448, in __call__
   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
367, in reval
   for arg in args: self._put(arg, req_num)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
139, in _put
   else: self._putobj(obj, req_num)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
144, in _putobj
   self._write(o, pickle.dumps(obj, 1), req_num)
 File /usr/lib/python2.3/pickle.py, line 1386, in dumps
   Pickler(file, protocol, bin).dump(obj)
 File /usr/lib/python2.3/pickle.py, line 231, in dump
   self.save(obj)
 File /usr/lib/python2.3/pickle.py, line 293, in save
   f(self, obj) # Call unbound method with explicit self
 File /usr/lib/python2.3/pickle.py, line 614, in save_list
   self._batch_appends(iter(obj))
 File /usr/lib/python2.3/pickle.py, line 647, in _batch_appends
   save(x)
 File /usr/lib/python2.3/pickle.py, line 293, in save
   f(self, obj) # Call unbound method with explicit self
 File /usr/lib/python2.3/pickle.py, line 737, in save_inst
   stuff = getstate()
 File /usr/lib/python2.3/site-packages/rdiff_backup/rpath.py, line 754,
in __getstate__
   assert self.conn is Globals.local_connection

Traceback (most recent call last):
 File /usr/bin/rdiff-backup, line 23, in ?
   rdiff_backup.Main.error_check_Main(sys.argv[1:])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 295, in
error_check_Main
   try: Main(arglist)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 315, in
Main
   take_action(rps)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 271, in
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 328, in
Backup
   backup_final_init(rpout)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 425, in
backup_final_init
   checkdest_if_necessary(rpout)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 820, in
checkdest_if_necessary
   need_check = checkdest_need_check(dest_rp)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 810, in
checkdest_need_check
   if not force: curmir_incs[0].conn.regress.check_pids(curmir_incs)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
448, in __call__
   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
367, in reval
   for arg in args: self._put(arg, req_num)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
139, in _put
   else: self._putobj(obj, req_num)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
144, in _putobj
   self._write(o, pickle.dumps(obj, 1), req_num)
 File /usr/lib/python2.3/pickle.py, line 1386, in dumps
   Pickler(file, protocol, bin).dump(obj)
 File /usr/lib/python2.3/pickle.py, line 231, in dump
   self.save(obj)
 File /usr/lib/python2.3/pickle.py, line 293, in save
   f(self, obj) # Call unbound method with explicit self
 File /usr/lib/python2.3/pickle.py, line 614, in save_list
   self._batch_appends(iter(obj))
 File /usr/lib/python2.3/pickle.py, line 647, in _batch_appends
   save(x)
 File /usr/lib/python2.3/pickle.py, line 293, in save
   f(self, obj) # Call unbound method with explicit self
 File /usr/lib/python2.3/pickle.py, line 737, in save_inst
   stuff = getstate()
 File /usr/lib/python2.3/site-packages/rdiff_backup/rpath.py, line 754,
in __getstate__
   assert self.conn is Globals.local_connection
AssertionError
Fatal Error: Lost connection to the remote system


I'll try to upgrade to 1.1.12 in both, but do you knows what is this error?
Thanks


2007/7/26, Andrew Ferguson [EMAIL PROTECTED]:


Marcelo Diotto wrote:
 But i always get this error:

 Exception 'too many values to unpack' raised of class

Re: [rdiff-backup-users] Error: Too Many values to unpack

[Andrew Ferguson]

Marcelo Diotto wrote:
 But i always get this error:
 
 Exception 'too many values to unpack' raised of class

Marcelo,

You are not using the same version of rdiff-backup on both sides.

An important change was made to the network protocol in 1.1.12 to fix a
long-standing bug. If you use 1.1.12 on both sides, then you will not
have this problem.

Andrew

-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error: Too Many values to unpack

[Marcelo Diotto]

Hello Everybody,
  I'm trying to do the following command:

# rdiff-backup / alpha::/raid/marte

But i always get this error:

Exception 'too many values to unpack' raised of class 'exceptions.ValueError
':
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 299, in
error_check_Main
   try: Main(arglist)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 319, in
Main
   take_action(rps)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 275, in
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 329, in
Backup
   rpout.conn.fs_abilities.backup_set_globals(rpin)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
447, in __call__
   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
369, in reval
   if isinstance(result, Exception): raise result

Traceback (most recent call last):
 File /usr/bin/rdiff-backup, line 23, in ?
   rdiff_backup.Main.error_check_Main(sys.argv[1:])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 299, in
error_check_Main
   try: Main(arglist)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 319, in
Main
   take_action(rps)
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 275, in
take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /usr/lib/python2.3/site-packages/rdiff_backup/Main.py, line 329, in
Backup
   rpout.conn.fs_abilities.backup_set_globals(rpin)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
447, in __call__
   return apply(self.connection.reval, (self.name,) + args)
 File /usr/lib/python2.3/site-packages/rdiff_backup/connection.py, line
369, in reval
   if isinstance(result, Exception): raise result
ValueError: too many values to unpack
Fatal Error: Lost connection to the remote system

If i do an rdiff-backup /etc alpha::/raid/marte everything works fine, but
if i try rdiff-backup /home alpha::/raid/marte i get the same error again.
I have more than 1500 users and 85GB to backup. The strange thing was that
this backuyp worked for three days, and so it started to give these errors.

Thanks
Marcelo


--
--
:: Diotto.Net ::
http://www.diotto.net
Artigos, Notícias e Downloads sobre software livre e tecnologia em geral
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error: Too Many values to unpack

[Andrew Ferguson]

Marcelo Diotto wrote:
 Yes, that was the problem.
 Now i am with version 1.1.5 im both servers but i get this error:
 
 Exception '' raised of class 'exceptions.AssertionError':

I believe this is one of the bugs fixed after 1.1.5. Please don't use
earlier development versions. The latest one is always the most bug-free.

Thanks,
Andrew

-- 
Andrew Ferguson - [EMAIL PROTECTED]



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error : af_unix path too long

[roland]

afaik, rdiff-backup cannot handle unix domain sockets.
in most cases, it doesn´t give any sense to back them up, anyway. most 
applications will (re-)create those files at runtime.


try the following commandline option:

--exclude-sockets
 Exclude all socket files.

regards
roland


- Original Message - 
From: Thibaud Hulin [EMAIL PROTECTED]

To: rdiff-backup-users@nongnu.org
Sent: Friday, January 19, 2007 5:44 PM
Subject: [rdiff-backup-users] error : af_unix path too long



Hello !
Thanks for your good work with rdiff_backup !
I have a problem, when I lanuch rdiff-backup with my home folder, I obtain 
this error, and I can't update my record :


SpecialFileError run/dbus/system_bus_socket Socket error: AF_UNIX path too 
long
SpecialFileError run/mysqld/mysqld.sock Socket error: AF_UNIX path too 
long

Fatal Error: Bad rdiff-backup-data dir on destination side

The rdiff-backup data directory
/media/hda5/backup/home/rdiff-backup-data
exists, but we cannot find a valid current_mirror marker.  You can
avoid this message by removing the rdiff-backup-data directory;
however any data in it will be lost.

Probably this error was caused because the first rdiff-backup session
into a new directory failed.  If this is the case it is safe to delete
the rdiff-backup-data directory because there is no important
information in it.

I looked in the wiki documentation, but I couldn't fall help.

Thanks for ideas,
Thibaud.



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: 
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki 




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error no 22: What may be the cause?

[Juergen Starek]

Hello everyone,

when trying to invoke rdiff-backup in the most simple way (e.g.
rdiff-backup /home/myhomedir /media/myremoteharddrive), I get an error
with a less than obvious cause (at least for me):

=

Exception '[Errno 22] Invalid argument: 
'/media/sda1/.java/.userPrefs/_!\'8!cgn!#4!cwm!\')!;059;064!z!$g!.gl!(g!b;064h!()!;125;064s!\';064!;125;064!u!!!;125;064y!(;064!a;0640!(;096!cg!\';064!a;0640!\'8!cg;061;061''
 raised of class 'exceptions.OSError':
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 295, in 
error_check_Main
try: Main(arglist)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 315, in 
Main
take_action(rps)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 271, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup.Mirror(rpin, rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 38, in 
Mirror
DestS.patch(dest_rpath, source_diffiter)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 218, in 
patch
ITR(diff.index, diff)
  File /usr/lib/python2.4/site-packages/rdiff_backup/rorpiter.py, line 284, 
in __call__
branch.start_process(*args)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 601, in 
start_process
if diff_rorp.isdir(): self.prepare_dir(diff_rorp, self.base_rp)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 629, in 
prepare_dir
base_rp.mkdir()
  File /usr/lib/python2.4/site-packages/rdiff_backup/rpath.py, line 863, in 
mkdir
self.conn.os.mkdir(self.path)

Traceback (most recent call last):
  File /usr/bin/rdiff-backup, line 23, in ?
rdiff_backup.Main.error_check_Main(sys.argv[1:])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 295, in 
error_check_Main
try: Main(arglist)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 315, in 
Main
take_action(rps)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 271, in 
take_action
elif action == backup: Backup(rps[0], rps[1])
  File /usr/lib/python2.4/site-packages/rdiff_backup/Main.py, line 337, in 
Backup
backup.Mirror(rpin, rpout)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 38, in 
Mirror
DestS.patch(dest_rpath, source_diffiter)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 218, in 
patch
ITR(diff.index, diff)
  File /usr/lib/python2.4/site-packages/rdiff_backup/rorpiter.py, line 284, 
in __call__
branch.start_process(*args)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 601, in 
start_process
if diff_rorp.isdir(): self.prepare_dir(diff_rorp, self.base_rp)
  File /usr/lib/python2.4/site-packages/rdiff_backup/backup.py, line 629, in 
prepare_dir
base_rp.mkdir()
  File /usr/lib/python2.4/site-packages/rdiff_backup/rpath.py, line 863, in 
mkdir
self.conn.os.mkdir(self.path)
OSError: [Errno 22] Invalid argument: 
'/media/sda1/.java/.userPrefs/_!\'8!cgn!#4!cwm!\')!;059;064!z!$g!.gl!(g!b;064h!()!;125;064s!\';064!;125;064!u!!!;125;064y!(;064!a;0640!(;096!cg!\';064!a;0640!\'8!cg;061;061'

=

I am rather sure that I don't have a file with such a strange name there... 

The source file system is ext3fs, using utf-8 in filenames. The
destination filesystem is vfat.

Many thanks in advance for any hints

  Jürgen



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error backing up to NAS device

[David Kempe]

Hi Devraj,
how are you mounting the NAS device?

dave

Devraj Mukherjee wrote:

Hi everyone,

I am trying to use rdiff-backup to write to an NAS device and this is
wha tI get.




___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error backing up to NAS device

[Devraj Mukherjee]

Hi everyone,

I am trying to use rdiff-backup to write to an NAS device and this is
wha tI get.

Any ideas?

[EMAIL PROTECTED] ~]# rdiff-backup /www/apache2 /mnt/nas/www/apache2
Warning: ownership cannot be changed on filesystem at
/mnt/nas/www/apache2/rdiff-backup-data
Warning: hard linking not supported by filesystem at
/mnt/nas/www/apache2/rdiff-backup-data
Traceback (most recent call last):
 File /usr/bin/rdiff-backup, line 23, in ?
   rdiff_backup.Main.Main(sys.argv[1:])
 File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line
282, in Main
   take_action(rps)
 File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line
252, in take_action
   elif action == backup: Backup(rps[0], rps[1])
 File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line
293, in Backup
   backup_set_fs_globals(rpin, rpout)
 File /usr/lib64/python2.3/site-packages/rdiff_backup/Main.py, line
415, in backup_set_fs_globals
   dest_fsa = rpout.conn.fs_abilities.get_fsabilities_readwrite(
 File /usr/lib64/python2.3/site-packages/rdiff_backup/fs_abilities.py,
line 395, in get_fsabilities_readwrite
   return FSAbilities(desc_string).init_readwrite(
 File /usr/lib64/python2.3/site-packages/rdiff_backup/fs_abilities.py,
line 152, in init_readwrite
   if override_chars_to_quote is None: self.set_chars_to_quote(subdir)
 File /usr/lib64/python2.3/site-packages/rdiff_backup/fs_abilities.py,
line 263, in set_chars_to_quote
   sanity_check()
 File /usr/lib64/python2.3/site-packages/rdiff_backup/fs_abilities.py,
line 261, in sanity_check
   rp.delete()
 File /usr/lib64/python2.3/site-packages/rdiff_backup/rpath.py,
line 869, in delete
   else: self.conn.os.unlink(self.path)
OSError: [Errno 2] No such file or directory:
'/mnt/nas/www/apache2/rdiff-backup-data/rdiff-backup.tmp.1/5-_ a.'


--
I never look back, it distracts from the now, Edna Mode (The Incredibles)


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error: File changed from regular file before signature

[Randall Nortman]

I'm running rdiff-backup 0.12.8, because the system I'm backing up is
pretty ancient and I just haven't been motivated to upgrade it yet.  A
while back, one of my backups was interrupted, so the next time it ran
rdiff-backup had to regress the archive, and encountered an error:

Previous backup seems to have failed, regressing destination now.
Warning, metadata file has entry for var/spool/exim/input/1FQbbR-0007NJ-00-J,
but there are no associated files

Now, every time I run the backup, I get this:

UpdateError var/spool/exim/input/1FQbbR-0007NJ-00-J File changed from regular
file before signature

The rest of the backup works normally.  The file these messages refer
to no longer exists on the source system -- it was obviously just a
temporary file in Exim's queue.

I'm not sure where to look for this in the metadata.  Presumably, I
need to find it and delete it manually?  Or would this be handled
better by a newer version of rdiff-backup?  I'm willing to upgrade, I
just need a good excuse.

Thanks,

Randall


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error: File changed from regular file before signature

[dean gaudet]

On Sun, 21 May 2006, Randall Nortman wrote:

 I'm not sure where to look for this in the metadata.

look in the mirror_metadata file in the rdiff-backup-data subdirectory of 
the target... you could probably gunzip and edit away the entry for that 
file.

i think this one is fixed by later revs, but i'm not sure.

-dean


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Message

[Jim St.Cyr]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Escoto wrote:
 Jim St.Cyr [EMAIL PROTECTED]
 wrote the following on Sun, 29 Jan 2006 19:56:38 -0500
 I've been using the 1.1.5 version for a while now.  Is there any way to
 start writing the hashes or to verify that they are being written at
 all?  More important, am I stuck or should I downrev to an earlier version?
 
 You can zcat your mirror_metadata file and look for hashes.  There's no
 reason to downgrade.  rdiff-backup will only read a file during a backup
 session if it has changed.  If a file hasn't changed since you upgraded
 to 1.1.1 or later, then there still won't be a hash for that file
 available.
 
 

Ben-

I must have had some serious brain cramps.  It dawned on me that the
messages are informational; not indicative of a recovery failure.  When
I looked in the recovery directory this morning there they were, all the
files recovered back to the 21st.

Off to find a crow sandwich

Thanks again.

Jim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD3pOnG5749I43ocMRAr0MAJ91uO2Dj3aPdmGpEXK2fUOMS69elgCfWi1L
UXadS7Eq99X1QC36Uq7K8uw=
=n1Rj
-END PGP SIGNATURE-


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Message

[Ben Escoto]

 Jim St.Cyr [EMAIL PROTECTED]
 wrote the following on Wed, 25 Jan 2006 12:53:43 -0500

 I get an error message similiar to the following:
 
 Hash for Docs/WAN Policy 10.2.doc missing, cannot check
 
 A Google search has unearthed where the error message in the code is
 originating from but I haven't been able to find out what the message means
 and what (if anything) I can do to recover the data.
 
 I'm using rdiff-backup 1.1.5

By default, recent devel versions of rdiff-backup store SHA1 hashes of
all regular files, and it checks them when restoring.  Probably the
backup you are restoring was made by an earlier version of rdiff-backup,
which didn't write any hashes.


-- 
Ben Escoto


pgp6XmvbUBYXh.pgp
Description: PGP signature
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Message

[Jim St.Cyr]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Escoto wrote:
 Jim St.Cyr [EMAIL PROTECTED]
 wrote the following on Wed, 25 Jan 2006 12:53:43 -0500
 I get an error message similiar to the following:

 Hash for Docs/WAN Policy 10.2.doc missing, cannot check

 A Google search has unearthed where the error message in the code is
 originating from but I haven't been able to find out what the message means
 and what (if anything) I can do to recover the data.

 I'm using rdiff-backup 1.1.5
 
 By default, recent devel versions of rdiff-backup store SHA1 hashes of
 all regular files, and it checks them when restoring.  Probably the
 backup you are restoring was made by an earlier version of rdiff-backup,
 which didn't write any hashes.
 
 
Ben-

Thanks for the reply.

I've been using the 1.1.5 version for a while now.  Is there any way to
start writing the hashes or to verify that they are being written at
all?  More important, am I stuck or should I downrev to an earlier version?

Jim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD3WRGG5749I43ocMRAiCYAJ9e88li+LsyYvMfNGUmkajcj50ybACeMU5I
7e/elFCaRAKOGPgBnwwt3YQ=
=3wfp
-END PGP SIGNATURE-


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error Message

[Ben Escoto]

 Jim St.Cyr [EMAIL PROTECTED]
 wrote the following on Sun, 29 Jan 2006 19:56:38 -0500
 
 I've been using the 1.1.5 version for a while now.  Is there any way to
 start writing the hashes or to verify that they are being written at
 all?  More important, am I stuck or should I downrev to an earlier version?

You can zcat your mirror_metadata file and look for hashes.  There's no
reason to downgrade.  rdiff-backup will only read a file during a backup
session if it has changed.  If a file hasn't changed since you upgraded
to 1.1.1 or later, then there still won't be a hash for that file
available.


-- 
Ben Escoto


pgpIzTSVzZlMA.pgp
Description: PGP signature
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error Message

[Jim St.Cyr]

Hello-

I've been backing up a directory using the command:

/usr/bin/rdiff-backup --print-statistics /mnt/server5b_e$/Users/Common/IRM_Common /raid5/backup/server5b/IRM_Users


I'm attempting to recover a subdirectory using the command:

rdiff-backup -r 4D --force /raid5/backup/server5b/IRM_Users/MHowarth/ /raid5/backup/mel

I get an error message similiar to the following:

Hash for Docs/WAN Policy 10.2.doc missing, cannot check

A Google search has unearthed where the error message in the code is originating from but I haven't been able to find out what the message means and what (if anything) I can do to recover the data.

I'm using rdiff-backup 1.1.5

Thank you.

Jim
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error 107 while in patch cycle

[Gerard van Dijnsen]

Ok, some more on this bug. It seems rsync-backup successfully completes
the backup, but still generates this error. I compared the MD5 sums of
both the original file and the backup and they are identical. 

I added the complete backtrace of the error here:

python: ERROR: (rs_job_iter) internal error: job made no progress
[orig_in=1, or
ig_out=65536, final_in=1, final_out=65536]
Exception 'librsync error 107 while in patch cycle' raised of class
'rdiff_backup.librsync.librsyncError':
  File /usr/lib/python2.4/site-packages/rdiff_backup/robust.py, line
32, in check_common_error
try: return function(*args)
  File /usr/lib/python2.4/site-packages/rdiff_backup/Rdiff.py, line
86, in patch_local
if outrp: outrp.write_from_fileobj(patchfile)
  File /usr/lib/python2.4/site-packages/rdiff_backup/rpath.py, line
980, in write_from_fileobj
copyfileobj(fp, outfp)
  File /usr/lib/python2.4/site-packages/rdiff_backup/rpath.py, line
58, in copyfileobj
inbuf = inputfp.read(blocksize)
  File /usr/lib/python2.4/site-packages/rdiff_backup/librsync.py, line
76, in read
self._add_to_outbuf_once()
  File /usr/lib/python2.4/site-packages/rdiff_backup/librsync.py, line
87, in _add_to_outbuf_once
except _librsync.librsyncError, e: raise librsyncError(str(e))

UpdateError usr/local/samba/debank/rest/films/De dominee/DE_DOMINEE.ISO
librsync error 107 while in patch cycle

On Thu, 2006-01-12 at 10:41 +0100, gerard van Dijnsen wrote:
 Hi all,
 
 Using rdiff-backup with some large files (4 Gb) I get the following error:
 
 UpdateError filename librsync  error 107 while in patch cycle
 
 Googling around I found out that it may be an error with librsync 9.7. Can you
 confirm this? And does a patch exist?
 
 Regards,
 
 Gerard
 
 
 
 ___
 rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
 Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] error 107 while in patch cycle

[Ben Escoto]

 Gerard van Dijnsen [EMAIL PROTECTED]
 wrote the following on Fri, 13 Jan 2006 22:08:26 +0100
 Ok, some more on this bug. It seems rsync-backup successfully completes
 the backup, but still generates this error. I compared the MD5 sums of
 both the original file and the backup and they are identical. 

rdiff-backup seems just to be reporting the error 107 given to it by
librsync.  I've read a few threads on this, but no one was able to
figure it out.

If you want to get to the bottom of this, you could try making sure
the error is reproduceable.  Then you could use 'rdiff' to perform the
relevant patching/diffing/signing operations without rdiff-backup, to
see if the problem had anything to do with rdiff-backup.


-- 
Ben Escoto


pgpQfuBTdX2TK.pgp
Description: PGP signature
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] error 107 while in patch cycle

[gerard van Dijnsen]

Hi all,

Using rdiff-backup with some large files (4 Gb) I get the following error:

UpdateError filename librsync  error 107 while in patch cycle

Googling around I found out that it may be an error with librsync 9.7. Can you
confirm this? And does a patch exist?

Regards,

Gerard



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error when doing restore

[Davy Durham]

Okay thanks.. well I saw that error, but it didn't mean anything to me, 
but I guess that's because I didn't read it.


The weird thing is that I reran the backup manually and that fixed it 
with no --check-backup-dir directory.. but when it did run, it did a lot 
of unusual things like deleting increment files.   


Anyhow, it's working great again.

Thanks

Ben Escoto wrote:


Davy Durham [EMAIL PROTECTED]
wrote the following on Sun, 01 Jan 2006 02:08:26 -0600
   

I'm getting the following output (using -v9) when attemping to do a 
restore.. there is no apparent reason for the error:


Any ideas?
   


...

The -v1 output would probably have been more informative, because then
you would have only seen the error message:

 


Fatal Error: Previous backup to /home/backup/data/source_machine/.
seems to have failed.  Rerun rdiff-backup with
--check-destination-dir option to revert directory to state before
unsuccessful session.
   



rdiff-backup quits restoring if the destination in the middle of a
backup (e.g. because previous backup failed, or is still going).


 





___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

[rdiff-backup-users] Error recovering from failed backup

[Keith Edmunds]

I have a server being backed up by rdiff-backup, and occasionally the 
backup fails for network or other reasons. The problem I am experiencing 
happens on the _next_ backup. The command issued is:


--
rdiff-backup --print-statistics --create-full-path \
/home/xxx \
backup::/backups/yyy/xxx \
--

Then I get, as expected:

--
Previous backup seems to have failed, regressing destination now.
--

Followed by:

--
Warning: Could not restore file /backups/yyy/xxx/02LaidOut/.DS_Store!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
-

Note that the source directory name is '02 Laid Out' but that the spaces 
have disappeared in the error message (but the spaces do exist on the 
backup:: machine). The exclamation mark at the end of the error message 
is part of the message rather than part of the filename. Both source and 
destination machines are running Linux with rdiff-backup 0.13.4. The 
files being backed up are created by Apple Macs and saved in an 
Appletalk share.


Any clues as to how to proceed?

Thanks,
Keith


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error recovering from failed backup

[Ben Escoto]

 Keith Edmunds [EMAIL PROTECTED]
 wrote the following on Thu, 08 Sep 2005 08:46:28 +0100
 --
 Warning: Could not restore file /backups/yyy/xxx/02LaidOut/.DS_Store!
 
 A regular file was indicated by the metadata, but could not be
 constructed from existing increments because last increment had type
 None.  Instead of the actual file's data, an empty length file will be
 created.  This error is probably caused by data loss in the
 rdiff-backup destination directory, or a bug in rdiff-backup
 -
 
 Note that the source directory name is '02 Laid Out' but that the spaces 
 have disappeared in the error message (but the spaces do exist on the 
 backup:: machine).

What does your metadata file say?  (e.g. zless
mirror_metadata.date.snapshot.gz, then search for that file)  If all
the files are still there you could either manually edit your metadata
file or move the directories around so they are in sync.

I don't know how this could have happened in the first place though.


-- 
Ben Escoto


pgp5fvJwtbdLx.pgp
Description: PGP signature
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Re: [rdiff-backup-users] Error message with Extended Attributes

[Paul Cuttriss]

-

  
Detected abilities for source (read only) file system:
  Extended attributes  On

  
  ...
  
  
Detected abilities for destination (read/write) file system:
  Extended attributes  Off

  
  
rdiff-backup checks to see if it can read and write EAs on the
destination filesystem, but only tries to list one on the source.
Here is the relevant code:


So if you want to see what is going on you could try testing xattr's
listxattr, setxattr, and getxattr from the python interpreter.


  

On the nail Ben

I had the filesystem mounted with the acl option, but not the
user_xattr option.

Once I remounted the filesystem with 'all' the necessary options it
worked a treat.
/dev/mapper/vg-backup on /backup type ext3 (rw,noatime,acl,user_xattr)

Thanks

Paul C


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki