Bug 5680 - triggering io.c:188: got_flist_entry_status: Assertion
Summary: triggering io.c:188: got_flist_entry_status: Assertion
Status: RESOLVED WORKSFORME
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.0.3
Hardware: x64 Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-08 14:20 UTC by Will Partain
Modified: 2011-02-22 11:01 UTC (History)
0 users

See Also:


Attachments
Extra debugging in place of the cited assert (653 bytes, patch)
2008-08-09 12:00 UTC, Wayne Davison
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Will Partain 2008-08-08 14:20:56 UTC
Precisely:
io.c:188: got_flist_entry_status: Assertion `flist != ((void *)0)' failed.

A long-standing rsync-y cronjob has started failing the last few days.  Fedora9 rsync (3.0.3); I got a similar error w/ 3.0.2.  2.6.9 does the same job fine.

A script that tidies up yyyy-mm-dd backup dirs runs (e.g.):

/usr/bin/rsync   -H --archive --delete --exclude='*.msf' --exclude=.cache --exclude=.svn --exclude=Trash --exclude=WebStatistics.txt --exclude=WebStatistics.txt,v --exclude=cyrus.cache --exclude=cyrus.index --exclude=cyrus.squat --exclude=spam-virii --exclude=spam05-08 --exclude=spam09-15 --exclude=spam16plus --exclude=willow-house-home-dir --delete-excluded --compare-dest=../2008-08-05 --compare-dest=../2008-08-06 --compare-dest=../2008-08-07 --compare-dest=../2008-08-08 2008-08-04/ 2008-08-04.tmp
Comment 1 Wayne Davison 2008-08-09 12:00:07 UTC
Created attachment 3463 [details]
Extra debugging in place of the cited assert

This replaces the assert with some info on the ndx value and what values are currently "live".
Comment 2 Wayne Davison 2008-08-09 12:01:53 UTC
I'd like to know what the output is with the extra-debugging patch applied (as it will tell us if the ndx value is corrupt or if something weird is going on).

It would also be good to give 3.0.4pre2 a try and see if the error recurs.  In either case, adding some extra -v options to get debug info may help to narrow down what rsync is doing at the time.  Feel free to email me debug data if you don't want to attach it to this bug.
Comment 3 Wayne Davison 2011-02-22 11:01:27 UTC
If you have more info, feel free to supply it.  In the meantime, I'm closing this.