rsync failed, BiT is unforgiving

[Steffen Neumann]

Hi,

I have a similar problem already reported in various
other reports, which have been closed by now.
My BiT is 0.9.99.64~karmic, the snapshot fails,
and if I run rsync manually I find the culprit. It is caused
by bug #/372014 in ecryptfs, and seems to occur for quite some people.

I report the problem because I think that one broken file
should not abort the whole backup process, leaving me
without any backup at all (This complaint was also raised by
a different report I am currently unable to find).

IIRC BiT did (silently) ignore rsync errors earlier, which was also problematic (#507246).
Maybe with the new log view feature some more forgiveness can be (re-)added ?
At least I'd like those IO errors to be ignored, which happen to me
all too often with ecryptfs.

Yours,
Steffen

  home/sneumann/
  IO error encountered -- skipping file deletion
  ....
  rsync: send_files failed to open "/home/sneumann/.bash_history": Input/output error (5)
  ....
  rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1060) [sender=3.0.7]

[Dan (danleweb)]

OK, you are not the first to ask this, so I should add an option "continue on errors".