I suspect, but have not figured out yet, that this is due to the new
striping code (even on images that don't have advanced striping
enabled). I know we want to look at it further; it might be that this
is a regression.
On 12/07/2012 07:44 PM, Henry C Chang wrote:
Hi,
I am testing v0.55. I noticed that the behavior of
librbd::Image::read_iterate() changed. With 0.48.2, when hitting the
hole, the callback function will be called with the buf set to NULL.
However, with v0.55, I got the zero-ed buffer of full length of the
object (e.g., 4MB).
Is it the expected behavior or a bug?
Henry
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
