On Wed, Mar 16, 2016 at 11:27 AM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: > > ../ceph-object-corpus/archive/0.61.4-60-g24c59be/objects/RGWBucketEnt > > ../ceph-object-corpus/archive/0.61.4-60-g24c59be/objects/RGWBucketInfo > error: buffer::end_of_buffer > **** failed to decode > ../ceph-object-corpus/archive/0.61.4-60-g24c59be/objects/RGWBucketInfo/25f5ff183bba6da708243a0bbbe40a2e > **** > error: buffer::end_of_buffer > **** failed to decode > ../ceph-object-corpus/archive/0.61.4-60-g24c59be/objects/RGWBucketInfo/54f53e3e301071f48247d59272b27b53 > **** > > ../ceph-object-corpus/archive/0.61.4-60-g24c59be/objects/rgw_bucket_pending_info > > "Just" a matter of rebase? > Or does it need more tinkering. Well, ceph-object-corpus is a bunch of old encoded versions of our objects, and it's validating that current code is still capable of decoding them. 0.61.4 is pretty old but I *think* should still work (maybe check that your submodules are all up to date; maybe some of them got dropped?). Assuming that still works on Linux, it's not a rebase problem; I would guess maybe these types just never worked because it wasn't BSD cross-compatible until more recently. You might want to explore how they're failing exactly; obviously it's running out of data to decode but the *why* is interesting. -Greg -- 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
