Comment 2 for bug 832052

Hi,

This is a dupe of bug 413430 which basically says a file has been truncated - typically this happens because of an OS error or disk error or a machine crash.

In 2.4.0 we started flushing files to disk by default after they're written, which was intended to reduce the frequency of this. So, it's possible this problem was introduced by an earlier client and just discovered by bzr 2.4.0, or perhaps our check is not enough, or perhaps something else.

Do you recall if your machine recently crashed or abruptly stopped or had any similar problem?

(fdatasync is not going to be enough on its own; continued incidents of this mean perhaps we need built in recovery.)