Under certain circumstances, copying an object onto itself (for example,
to change its metadata) produced a truncated object. The truncated object
had correct metadata, including the original size, but the underlying RADOS
object was smaller. Consequently, when a client attempted to fetch the
object, it received less data than indicated by the Content-Length header,
blocked for more, and eventually timed out. This bug has been fixed, and
the object can now be read successfully in the aforementioned scenario.