Re: More objects misplaced than exist?
Hi Anthony, answering also to the list... Am 16.01.25 um 15:52 schrieb Anthony D'Atri:
When I see anomalous status my first thought is to manually failover the mgr I stopped the active mgr, another took over, but still the status is the same:
data: volumes: 1/1 healthy pools: 4 pools, 2081 pgs objects: 3.53M objects, 12 TiB usage: 36 TiB used, 226 TiB / 262 TiB avail pgs: 17669564/10601739 objects misplaced (166.667%) 2081 active+clean+remapped What I still don't understand is: why does Ceph report usage 100% for all pools, which is nonsense? Can that be related to the confusing numbers of misplaces objects? root@pve01:~# ceph df --- RAW STORAGE --- CLASS SIZE AVAIL USED RAW USED %RAW USED ssd 262 TiB 226 TiB 36 TiB 36 TiB 13.58 TOTAL 262 TiB 226 TiB 36 TiB 36 TiB 13.58 --- POOLS --- POOL ID PGS STORED OBJECTS USED %USED MAX AVAIL .mgr 1 1 7.6 MiB 3 15 MiB 100.00 0 B ReplicationPool 2 1024 8.0 TiB 2.11M 24 TiB 100.00 0 B cephfs_data 7 1024 3.9 TiB 1.43M 12 TiB 100.00 0 B cephfs_metadata 8 32 268 MiB 143 804 MiB 100.00 0 B -- Andre Tann
Am 16.01.25 um 16:53 schrieb Andre Tann:
--- POOLS --- POOL ID PGS STORED OBJECTS USED %USED MAX AVAIL .mgr 1 1 7.6 MiB 3 15 MiB 100.00 0 B ReplicationPool 2 1024 8.0 TiB 2.11M 24 TiB 100.00 0 B cephfs_data 7 1024 3.9 TiB 1.43M 12 TiB 100.00 0 B cephfs_metadata 8 32 268 MiB 143 804 MiB 100.00 0 B
For the records: When moving OSDs in the crush location, I forgot to set root=default. But the crush rule wanted to take the default bucket in the first step, so it could not find OSDs anymore. -- Andre Tann
participants (1)
-
Andre Tann