2025-01-13T13:47:12.960Z | <Andrea Bolzonella> Hello, since upgrading to Squid, I am unable to use ceph-dencoder as I did before. It no longer allows me to decode anything. Is this behavior expected? |
2025-01-13T13:49:56.788Z | <Andrea Bolzonella> Also, is there a good reason why ceph-dencoder is gzipped in the official Docker image? |
2025-01-13T14:04:19.823Z | <Nitzan Mordechai> no, its not usual, what do you actually get? |
2025-01-13T14:21:16.002Z | <Andrea Bolzonella> ```root@alpha:~# rados -p cephfs_data getxattr 100000001fc.00000000 parent |ceph-dencoder type inode_backtrace_t import - decode dump_json
error: stray data at end of buffer, offset 121``` |
2025-01-13T14:25:00.231Z | <Andrea Bolzonella> same with
```root@alpha:~# ceph-dencoder type RGWObjManifest import manifest.bin decode
error: stray data at end of buffer, offset 344``` |
2025-01-13T15:08:04.199Z | <Nitzan Mordechai> can you please open new tracker for that? |
2025-01-13T15:30:47.717Z | <Andrea Bolzonella> Sure I will. About the why is the ceph-dencoder is gzipped in the docker image. do you know wahy? |
2025-01-13T15:31:16.764Z | <Nitzan Mordechai> i'm not sure about that one |
2025-01-13T15:49:05.091Z | <Andrea Bolzonella> <https://tracker.ceph.com/issues/69509> |
2025-01-13T16:07:41.506Z | <Nitzan Mordechai> @Andrea Bolzonella thanks! |
2025-01-13T17:43:33.849Z | <seenafallah> Hey all, I have a question regarding the new Ceph container builds after the ceph-container deprecation. Will the new releases, like v19.2.1, be built using the `Containerfile` in the Ceph repo? If so, is it okay that the `Containerfile` always points to a prerelease, like in this example: <https://github.com/ceph/ceph/blob/squid/container/Containerfile#L87>? |