Bug 6821 - Assertion failed so rsync crashes (path includes special char)
Assertion failed so rsync crashes (path includes special char)
Status: ASSIGNED
Product: rsync
Classification: Unclassified
Component: core
3.0.6
x86 FreeBSD
: P3 normal
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-16 16:39 UTC by Alex de Kruijff
Modified: 2011-01-01 16:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex de Kruijff 2009-10-16 16:39:05 UTC
I've run the following command: rsync -naHe "/usr/bin/ssh -i /root/.ssh/id_dsa_gateway" --compress-level=9 --stats Server1-*-2009-10-* REMOTE:/backup/

After a wile it gives me this and aborts:

rsync: stat "/path/directory/!path with spaces/FILE.EXT" failed: No such file or directory (2)
message repeated 20 to 50 times
Assertion failed: (CVAL(node->data, 0) == 0), function finish_hard_link, file hlink.c, line 533.
rsync: stat "/path/directory/!path with spaces/FILE.EXT" failed: No such file or directory (2)
message repeated about 5 times.
rsync error: unexplained error (code 134) at io.c(1143) [sender=3.0.6]

# rsync --version
rsync  version 3.0.6  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, no iconv, symtimes
Comment 1 Wayne Davison 2011-01-01 16:13:04 UTC
Rsync 3.0.7 has this fix which is probably the cause of all the "No such file or directory" errors:

    - Avoid an error when --dry-run  was trying to stat a prior hard-link file
      that hasn't really been created.

The assertion failure is something I haven't yet managed to reproduce.  I have added more descriptive messages into the code for 3.0.8 that may help to narrow down what is happening.