verbosity with respect to rsync errors

Hi,

I am recursively suffering the following error when trying to make my backups, but I don't know how to fix it:

[E] Error: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
[E] Failed to take snapshot 10/29/10 12:00:08 !!!

From some bugs reported in launchpad, it seems that the reason is the attributes of some files/folders that rsync doesn't like. Btw, I run backintime as root because I want to make backups of the whole system (I discard though /dev /proc /sys and my $HOME because it is encrypted, so I just save the encrypted version of it).

The problem is that I don't know how to find which file/-s or folder/-s are generating those issues. There is not any info for it in the log files. I would really appreciate if you can indicate some strategy to follow because all I tried didn't result.

I wonder whether it could be possible to run rsync within backintime with different degrees of verbosity and save such information in the logs. Of course this would increase the time that backintime needs to make a backup, and this doesn't have to be used if everything goes just fine. So I would suggest to put it as an option to enable only when some error has happened before in order to allow a much more efficient exploration of the errors.

On other hand, not related to this at all, I wonder if it would be possible to indicate somehow the expected time to finish when making manual backups.

Thanks in advance