John Mulligan

I started looking into this and it doesn't look too challenging. In many ways it's similar to our existing diff iterate support. However, what's not clear to me is why...

I've created a preliminary implementation at #624. At this time I can't reproduce the behavior of hole detection that the function in ceph is noted to have. I'll look into...

https://tracker.ceph.com/issues/3619 It appears that the sparse file "hole" detection does not work properly. And it has not for a while. I can implement it without unit tests to verify hole...

It's been over two weeks since I checked up on the requirement to detect "holes". Based on the non-response I think I will abandon PR #624 since without hole detection...

See a previous attempt at adding something for this in PR #84

Poking around a bit more, and it appears this isn't in any released versions of ceph yet, not even octopus, so it would appear we'd need to wait a while...

Thanks! CCing @leseb and @thotz as our experts on rgw for scoping. If either of think it's a good fit for go-ceph we'll label this issues appropriately.

I started cleaning up some of this a while back, but should probably continue it!

Could you please post links to the features/tools in question? I'm not familiar with ceph-dencoder and just saying "encode/decode" could mean a lot of different things.

OK, I've also now looked at https://docs.ceph.com/en/latest/man/8/ceph-dencoder/ and have a rough idea of what the tool does. Unfortunately, I don't quite see how this fits in the grand scheme of...