rsync - Sep 2009 - rsync finds files to sync which don't exist and then crashes

Hello,
I'm running the following script for backup:
SHORTHOST=`hostname | awk 'BEGIN { FS="." } { print $1 }'`
cd $HOME || exit 1
rsync --ignore-errors  --max-size=50m  -v --delete --delete-excluded
--log-file=/tmp/backup.log --exclude-from=$HOME/.rsync/exclude \
  --timeout=3 -az \
  $HOME atticserve:/mnt/store/backup/$SHORTHOST

At some point it tries to sync the following file:
stefaan/Pictures/2009-08-29/P1000908.JPG

This file does not exist, although it used to. At this point rsync crashes
with:
2009/09/26 23:39:26 [27867] .d..t...... stefaan/
2009/09/26 23:39:27 [27867] .d..t...... stefaan/Pictures/2009-08-29/
2009/09/26 23:40:04 [27867] rsync: writefd_unbuffered failed to write 4
bytes [sender]: Broken pipe (32)
2009/09/26 23:40:04 [27867] rsync error: timeout in data send/receive (code
30) at io.c(200) [receiver=3.0.5]
2009/09/26 23:40:04 [27867] rsync: connection unexpectedly closed (1535
bytes received so far) [sender]
2009/09/26 23:40:04 [27867] rsync error: error in rsync protocol data stream
(code 12) at io.c(600) [sender=3.0.5]

I've fsck'd file system. No problems?
Anyone have a clue?

Thanks,
Stefaan

the log file is:


-- 
View this message in context:
http://www.nabble.com/rsync-finds-files-to-sync-which-don%27t-exist-and-then-crashes-tp25629110p25629110.html
Sent from the Samba - rsync mailing list archive at Nabble.com.

On Sat, 2009-09-26 at 14:45 -0700, stefaan wrote:
> I'm running the following script for backup:
> SHORTHOST=`hostname | awk 'BEGIN { FS="." } { print $1
}'`
> cd $HOME || exit 1
> rsync --ignore-errors  --max-size=50m  -v --delete --delete-excluded
> --log-file=/tmp/backup.log --exclude-from=$HOME/.rsync/exclude \
>   --timeout=3 -az \
>   $HOME atticserve:/mnt/store/backup/$SHORTHOST
> 
> At some point it tries to sync the following file:
> stefaan/Pictures/2009-08-29/P1000908.JPG
> 
> This file does not exist, although it used to.
That's really strange and smells of flakiness with the filesystem.  How
specifically did you check that the file does not exist: ls?  Does
"rsync --list-only" show the file?  It may help to run the sending
side
of rsync under strace to see its exact interaction with the filesystem.

-- 
Matt