Rsync dies with "Invalid file index:" error message
fra.nospam.nk at gmx.de
Sat Jun 24 13:03:10 GMT 2006
i'm having a rather strange problem with rsync (v2.6.8). Rsync is run to synchronize
two identical, rather old Solaris 2.6 servers. All filesystems rsync fine except for one.
Rsync bails out on this particular FS with the following messages:
# /var/tmp/bin/rsync -avz -e "ssh -i $keyfile" --exclude-from=/tmp/rsync_data.excl server:/data/ /data
receiving file list ... done
Invalid file index: 1610612736 (count=214) [sender]
rsync error: protocol incompatibility (code 2) at sender.c(169) [sender=2.6.8]
rsync: connection unexpectedly closed (4902 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [receiver=2.6.8]
rsync: connection unexpectedly closed (4861 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]
What i have tried so far, unfortunately to no avail:
- Nightly rsync build (2.6.9) from thursday won't help.
- Sending and receiving side FS have plenty space (69% free) and enough free inodes.
- Other FS with similar characteristics rsync fine. So i guess it's not a network related
- Ran fsck on umounted FS.
- Excluding the dir in the above example won't help. The behaviour is with all dirs in the FS.
- The FS in question is not under heavy use, just a lot of small files (41% inodes used).
- Restricting rsync to one dir on the FS (e.g. the sendfile dir in the above example) shows
rsync wants to transfer 214 objects. A 'find sendfile/ | wc -l' shows that there are actually
211 objects in this dir. It this normal behaviour?
Anyone got any suggestions?
Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
More information about the rsync