DO NOT REPLY [Bug 5407] New: hlink.c:480: finish_hard_link:
Assertion `flist != ((void *)0)' failed.
samba-bugs at samba.org
samba-bugs at samba.org
Tue Apr 22 01:19:24 GMT 2008
https://bugzilla.samba.org/show_bug.cgi?id=5407
Summary: hlink.c:480: finish_hard_link: Assertion `flist !=
((void *)0)' failed.
Product: rsync
Version: 3.0.2
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: brian_lindholm at users.sourceforge.net
QAContact: rsync-qa at samba.org
Running command-line as follows:
rsync --stats --modify-window=30 --links --hard-links --verbose --times -P -p \
--recursive --delete --exclude="known_hosts" --exclude=".Xauthority" \
--exclude=".ssh" /home/archive /backup/archive
Get the following error message:
rsync: hlink.c:480: finish_hard_link: Assertion `flist != ((void *)0)' failed.
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: unlink "/home/archive/Sermons_1/Music" failed: Is a directory (21)
unexpected tag 107 [sender]
rsync error: unexplained error (code 134) at io.c(1169) [sender=3.0.2]
Rsync reports a failure when attempting to unlink a directory on the *SOURCE*
side. I didn't ask it to delete *anything* on the source side. Holy crap!
Unfortunately, the error is not repeatable. A repeat of the command finished
the transfer without incident.
This error happens about one out of 20 rsync runs. It's been present since
rsync-3.0.0. I never saw anything like it with rsync-2.6.9.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the rsync
mailing list