9, rum S14
From: Ramin Najjarbashi
Sent: Tuesday, October 31, 2023 11:22 AM
To: Frank Schilder
Cc: Eugen Block; ceph-users@ceph.io
Subject: Re: [ceph-users] Re: find PG with large omap object
https://gist.github.com/RaminNietzsche/b8702014c333f3a44a995d5a6d4a56be
On Mon, Oc
> AIT Risø Campus
> Bygning 109, rum S14
>
>
> From: Eugen Block
> Sent: Monday, October 16, 2023 2:41 PM
> To: Frank Schilder
> Cc: ceph-users@ceph.io
> Subject: Re: [ceph-users] Re: find PG with large omap ob
Subject: Re: [ceph-users] Re: find PG with large omap object
Hi Frank,
> # jq '[.pg_stats[] | {"id": .pgid, "nk": .stat_sum.num_omap_keys}] |
> sort_by(.nk)' pgs.dump | tail
> },
> {
> "id": "12.17b",
> "nk": 1493776
>
ld not be there.
Do you have an idea how to continue diagnosis from here apart from
just trying a deep scrub on all PGs in the list from the log?
Thanks and best regards,
=====
Frank Schilder
AIT Risø Campus
Bygning 109, rum S14
From: Eugen Block
Sent: Monday, Oc
===
Frank Schilder
AIT Risø Campus
Bygning 109, rum S14
________
From: Eugen Block
Sent: Monday, October 16, 2023 1:41 PM
To: ceph-users@ceph.io
Subject: [ceph-users] Re: find PG with large omap object
Hi,
not sure if this is what you need, but if you know the p
Hi,
not sure if this is what you need, but if you know the pool id (you
probably should) you could try this, it's from an Octopus test cluster
(assuming the warning was for the number of keys, not bytes):
$ ceph -f json pg dump pgs 2>/dev/null | jq -r '.pg_stats[] | select
(.pgid |
