stevenhettrich@discoverfinancial.com
2004-Nov-09 17:10 UTC
redoing error causes backup file failure on target
It looks like rsync 2.5.4 vs 26 has a bug when the target file is backed up with a suffix. For a large 1 GB file transfer, an error "redoing" appeared in the debug. In other words, when you see redoing in your debug expect the backup not to have worked correctly. I didn't see this problem btwn naxpap01 and rwxp25l1 just btwn rwxp25l1 and naxp18l1. I'm pulling the code from source to target. In this example, 4,10,11 were all marked as redoing this created a AccChkpt.gz.r_bck the same as source and target. In other words, we lost our n-1 backed up file AccChkpt.gz for acc.4,10, and 11. Here is my syntax: b for backup and .r_bck for the backup suffix to append rsync -vvabc -e ssh --suffix=.r_bck --exclude '*.r_bck' \ --delete --delete-after ${user}@${shost}:$y $y $ grep redo * rsync0.ksh.log:redoing /pattern/acc.4/AccChkpt.gz(0) rsync0.ksh.log:redoing /pattern/acc.10/AccChkpt.gz(0) rsync0.ksh.log:redoing /pattern/acc.11/AccChkpt.gz(0) pattern/acc.6/AccChkpt.gz backed up /pattern/acc.9/AccChkpt.gz to /pattern/acc.9/AccChkpt.gz.r_bck total: matches=419 tag_hits=665438078 false_alarms=31317 data=1057222841 wrote 389599 bytes read 1057353840 bytes 823467.60 bytes/sec total size is 1064087737 speedup is 1.10 backed up /pattern/acc.4/AccChkpt.gz to /pattern/acc.4/AccChkpt.gz.r_bck redoing /pattern/acc.4/AccChkpt.gz(0) /pattern/acc.4/AccChkpt.gz backed up /pattern/acc.10/AccChkpt.gz to /pattern/acc.10/AccChkpt.gz.r_bck redoing /pattern/acc.10/AccChkpt.gz(0) backed up /pattern/acc.2/AccChkpt.gz to /pattern/acc.2/AccChkpt.gz.r_bck target file was OK: $ ls -alrt acc.*/AccCh* | grep -v r_bc -rw-r----- 1 pattern pattappl 1064087737 Nov 7 01:59 acc.9/AccChkpt.gz -rw-r----- 1 pattern pattappl 1066818822 Nov 7 01:59 acc.5/AccChkpt.gz -rw-r----- 1 pattern pattappl 1068174949 Nov 7 01:59 acc.10/AccChkpt.gz -rw-r----- 1 pattern pattappl 1062181981 Nov 7 01:59 acc.4/AccChkpt.gz (n) -rw-r----- 1 pattern pattappl 1061236249 Nov 7 01:59 acc.1/AccChkpt.gz -rw-r----- 1 pattern pattappl 1064009176 Nov 7 02:00 acc.0/AccChkpt.gz -rw-r----- 1 pattern pattappl 1067645375 Nov 7 02:00 acc.7/AccChkpt.gz -rw-r----- 1 pattern pattappl 1067315294 Nov 7 02:00 acc.8/AccChkpt.gz -rw-r----- 1 pattern pattappl 1069433318 Nov 7 02:00 acc.6/AccChkpt.gz -rw-r----- 1 pattern pattappl 1070707801 Nov 7 02:00 acc.3/AccChkpt.gz -rw-r----- 1 pattern pattappl 1072212331 Nov 7 02:00 acc.2/AccChkpt.gz -rw-r----- 1 pattern pattappl 1072031323 Nov 7 02:00 acc.11/AccChkpt.gz This error effects only the target backed up files using the suffix *.r_bck notice acc.4,10,11 have current time stamp like above even though they are suffix'd $ ls -alrt acc.*/AccCh* | grep r_bc -rw-r----- 1 pattern pattappl 1060894508 Nov 6 01:59 acc.1/AccChkpt.gz.r_bck (correct as n-1 or Nov 6th) -rw-r----- 1 pattern pattappl 1063737321 Nov 6 01:59 acc.9/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1071873948 Nov 6 01:59 acc.2/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1063662943 Nov 6 02:00 acc.0/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1069081019 Nov 6 02:00 acc.6/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1070370071 Nov 6 02:00 acc.3/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1066979615 Nov 6 02:00 acc.8/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1066477532 Nov 6 02:00 acc.5/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1067314365 Nov 6 02:00 acc.7/AccChkpt.gz.r_bck -rw-r----- 1 pattern pattappl 1068174949 Nov 7 01:59 acc.10/AccChkpt.gz.r_bck <error occurred here -rw-r----- 1 pattern pattappl 1062181981 Nov 7 01:59 acc.4/AccChkpt.gz.r_bck <<< error -rw-r----- 1 pattern pattappl 1072031323 Nov 7 02:00 acc.11/AccChkpt.gz.r_bck <<<< error Steven Hettrich Discover Financial Services Unix Applications Engineering (224)-405-0638 -------------- next part -------------- HTML attachment scrubbed and removed
On Tue, Nov 09, 2004 at 11:06:54AM -0600, stevenhettrich@discoverfinancial.com wrote:> In other words, we lost our n-1 backed up file AccChkpt.gz for > acc.4,10, and 11.Version 2.6.3 fixed this backup bug. You'll find it mentioned in the release notes: http://rsync.samba.org/ftp/rsync/rsync-2.6.3-NEWS Thanks for the report, ..wayne..
Maybe Matching Threads
- rsync compression (-z) and timestamp
- Redoing FAQ
- [LLVMdev] Any way get debug output of generated assembly from MCJIT without completely redoing CodeGen?
- [LLVMdev] Any way get debug output of generated assembly from MCJIT without completely redoing CodeGen?
- how do you redo the LABEL tag so the machine boots