large rsync fails with assertion error

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

large rsync fails with assertion error

Ken Chase
rsyncing a tree of perhaps 30M files, getting this:                                      
                                                                                         
rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.      
                                                                                         
then a bit more output and the parent catches up to the child:                            
                                                                                         
rsync: writefd_unbuffered failed to write 8 bytes to message fd [receiver]: Broken pipe  
(32)                                                                                      
rsync error: error in rsync protocol data stream (code 12) at io.c(1532) [receiver=3.0.9]
                                                                                         
it's from a remote system. No errors visible (kernel or otherwise) on either end.        
Hints?                                                                                    
                                                                                         
source:                                                                                  
rsync  version 3.1.1  protocol version 31                                                
                                                                                         
dest, where commands are issued from:                                                    
rsync  version 3.0.9  protocol version 30                                                
                                                                                         
ill have to try upgrading dest to 3.1.1 but its not in wheezy-backports                  
and dont really want to mess with this production machine too much.                      
                                                                                         
/kc                                                                                      
--
Ken Chase - Toronto Canada

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Reply | Threaded
Open this post in threaded view
|

Re: large rsync fails with assertion error

Ken Chase
Ok I found a bug about this:

https://bugzilla.samba.org/show_bug.cgi?id=6542

and it says fixed by upgrade. I found a way to upgrade. Using:

rsync  version 3.1.1  protocol version 31
 on receiving side that issues the rsync command, and

rsync  version 3.1.1  protocol version 31
 on the remote sending side.

Im still getting the same thing:

rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.

/kc


On Wed, Sep 09, 2015 at 12:58:30AM -0400, Ken Chase said:
  >rsyncing a tree of perhaps 30M files, getting this:                                      
  >                                                                                          
  >rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.      
  >                                                                                          
  >then a bit more output and the parent catches up to the child:                            
  >                                                                                          
  >rsync: writefd_unbuffered failed to write 8 bytes to message fd [receiver]: Broken pipe  
  >(32)                                                                                      
  >rsync error: error in rsync protocol data stream (code 12) at io.c(1532) [receiver=3.0.9]
  >                                                                                          
  >it's from a remote system. No errors visible (kernel or otherwise) on either end.        
  >Hints?                                                                                    
  >                                                                                          
  >source:                                                                                  
  >rsync  version 3.1.1  protocol version 31                                                
  >                                                                                          
  >dest, where commands are issued from:                                                    
  >rsync  version 3.0.9  protocol version 30                                                
  >                                                                                          
  >ill have to try upgrading dest to 3.1.1 but its not in wheezy-backports                  
  >and dont really want to mess with this production machine too much.                      
  >                                                                                          
  >/kc                                                                                      
  >--
  >Ken Chase - Toronto Canada
  >
  >--
  >Please use reply-all for most replies to avoid omitting the mailing list.
  >To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
  >Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Reply | Threaded
Open this post in threaded view
|

Re: large rsync fails with assertion error - bug #11506 was #6542 not fixed

Ken Chase
I opened a new bug for this but didnt see it come across the list. I have a
file tree I can reproduce this on readily (tho it's quite huge :/ ).

Any way to get around this? This is a major travesty for a backup scripting
situation I have, I expect others to bump into this too.

new bug is

https://bugzilla.samba.org/show_bug.cgi?id=11506

i can execute specific tests if required and log output, please advise.

/kc

On Wed, Sep 09, 2015 at 01:42:20AM -0400, Ken Chase said:
  >Ok I found a bug about this:
  >
  >https://bugzilla.samba.org/show_bug.cgi?id=6542
  >
  >and it says fixed by upgrade. I found a way to upgrade. Using:
  >
  >rsync  version 3.1.1  protocol version 31
  > on receiving side that issues the rsync command, and
  >
  >rsync  version 3.1.1  protocol version 31
  > on the remote sending side.
  >
  >Im still getting the same thing:
  >
  >rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.
  >
  >/kc
  >
  >
  >On Wed, Sep 09, 2015 at 12:58:30AM -0400, Ken Chase said:
  >  >rsyncing a tree of perhaps 30M files, getting this:                                      
  >  >                                                                                          
  >  >rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed.      
  >  >                                                                                          
  >  >then a bit more output and the parent catches up to the child:                            
  >  >                                                                                          
  >  >rsync: writefd_unbuffered failed to write 8 bytes to message fd [receiver]: Broken pipe  
  >  >(32)                                                                                      
  >  >rsync error: error in rsync protocol data stream (code 12) at io.c(1532) [receiver=3.0.9]
  >  >                                                                                          
  >  >it's from a remote system. No errors visible (kernel or otherwise) on either end.        
  >  >Hints?                                                                                    
  >  >                                                                                          
  >  >source:                                                                                  
  >  >rsync  version 3.1.1  protocol version 31                                                
  >  >                                                                                          
  >  >dest, where commands are issued from:                                                    
  >  >rsync  version 3.0.9  protocol version 30                                                
  >  >                                                                                          
  >  >ill have to try upgrading dest to 3.1.1 but its not in wheezy-backports                  
  >  >and dont really want to mess with this production machine too much.                      
  >  >                                                                                          
  >  >/kc                                                                                      
  >  >--
  >  >Ken Chase - Toronto Canada
  >  >
  >  >--
  >  >Please use reply-all for most replies to avoid omitting the mailing list.
  >  >To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
  >  >Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html


--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html