failed assertion: too many hard links
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rsync (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
While running
rsync -avzxE --hard-links --bwlimit=100000 --delete mace:/proj/
I got the error messages that you see down at the bottom.
Note that the relevant file in the remote file system does indeed have a lot of links:
mace:~$ ls -l /proj/aesop/
-rw-rw---- 2610 gpk aesop 61 2010-08-20 09:20 /proj/aesop/
mace:~$
Papers/
Papers/
rsync: link "/2011/
rsync: hlink.c:537: finish_hard_link: Assertion `(((unsigned char *)(node->data))[0]) == 0' failed.
rsync.sh: line 7: 1171 Aborted rsync -avzxE --hard-links --bwlimit=100000 --delete mace:/proj/
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(1530) [receiver=3.0.7]
receiving incremental file list
./
rsync: link "/2011/
rsync: hlink.c:537: finish_hard_link: Assertion `(((unsigned char *)(node->data))[0]) == 0' failed.
rsync.sh: line 8: 1192 Aborted rsync -avzxE --hard-links --bwlimit=100000 --delete mace:/proj/aesop/ /2011/aesop/
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: rsync 3.0.7-2ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Wed Sep 14 11:53:39 2011
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)
| gpk (gpk-kochanski) wrote | #1 |
| James Page (james-page) wrote | #2 |
| Changed in rsync (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in rsync (Ubuntu): | |
| status: | Incomplete → Expired |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a newer Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 849873 and any other logs that are relevant for this particular issue.