Hello,
I started a new fresh ceph cluster and have the exact same problem and
also the slow op warnings.
I found this bug report that seems to be about this problem:
https://158.69.68.89/issues/46743
"... mgr/devicehealth: device_health_metrics pool gets created even
without any OSDs in the
On 2020-08-22 03:19, Michael Thomas wrote:
>> Yes, I do have different crush rules to help map certain types of data
>> to different classes of hardware (EC HDDs, replicated SSDs, replicated
>> nvme). The default crush rule for the device_health_metrics pool was
>> to use replication across any
On 8/11/20 2:52 AM, Wido den Hollander wrote:
On 11/08/2020 00:40, Michael Thomas wrote:
On my relatively new Octopus cluster, I have one PG that has been
perpetually stuck in the 'unknown' state. It appears to belong to the
device_health_metrics pool, which was created automatically by the
On 11/08/2020 00:40, Michael Thomas wrote:
On my relatively new Octopus cluster, I have one PG that has been
perpetually stuck in the 'unknown' state. It appears to belong to the
device_health_metrics pool, which was created automatically by the mgr
daemon(?).
The OSDs that the PG maps to
