Comment 9 for bug 665444

ok. these errors are new since BIT 1.0.2 -- upon examining my earlier snapshots (successful under earlier versions of BIT), i see that the files that are causing the errors now were NOT copied under earlier versions of BIT. this suggests that the implementation of BIT has changed from a default of "continue on error" to "fail on error". if this is true, it is likely that many people will encounter such errors and assume there is a bug in the new version of BIT. you might want to explicitly highlight this in the changelog or documentation.

based on this experience, i also have a feature suggestion: as you point out, setting BIT to "continue on error" is not something we want to do as a standard. however, it would be nice if BIT popped up a message at the end of a snapshot session and said, "the following errors occurred [list]. should BIT continue even with these errors? y/N?" the advantage of this is that a user can quickly scan the errors and decide they are either significant or trivial -- and then choose whether partial or no backup is appropriate for the specific snapshot session.