What steps will reproduce the problem?
Unclear yet. Usually operation over several hours, sometimes under
increased system load by other processes on the machine.
What is the expected output?
Termination of costream with file inconstency message, a trace in the ecd
log files of similar flavour.
Problem description: At various places in the code, read(2) statements are
called without proper handling of return values where less than the file
size or requested buffer size are filled into the buffer. This results in a
failure of content consistency checks, and a subsequent abort of the normal
flow.
At some parts in the code, the problem is addressed by reading the length
of a file with a stat command, but it seems a bit bulky to implement that
for all read attempts.
Suggestions welcome.
Original issue reported on code.google.com by
christia...@gmail.comon 9 Nov 2008 at 10:20