On 1/30/19 9:08 PM, David Zafman wrote:
>
> Strange, I can't reproduce this with v13.2.4. I tried the following
> scenarios:
>
> pg acting 1, 0, 2 -> up 1, 0 4 (osd.2 marked out). The df on osd.2
> shows 0 space, but only osd.4 (backfill target) checks full space.
>
> pg acting 1, 0, 2 ->
Strange, I can't reproduce this with v13.2.4. I tried the following
scenarios:
pg acting 1, 0, 2 -> up 1, 0 4 (osd.2 marked out). The df on osd.2
shows 0 space, but only osd.4 (backfill target) checks full space.
pg acting 1, 0, 2 -> up 4,3,5 (osd,1,0,2 all marked out). The df for
On 1/25/19 8:33 AM, Gregory Farnum wrote:
> This doesn’t look familiar to me. Is the cluster still doing recovery so
> we can at least expect them to make progress when the “out” OSDs get
> removed from the set?
The recovery has already finished. It resolves itself, but in the
meantime I saw
I've also seen this effect a few times since Mimic (never happened in
Luminous). It always resolved itself but the HEALTH_ERROR can be
confusing to users.
Paul
--
Paul Emmerich
Looking for help with your Ceph cluster? Contact us at https://croit.io
croit GmbH
Freseniusstr. 31h
81247 München
This doesn’t look familiar to me. Is the cluster still doing recovery so we
can at least expect them to make progress when the “out” OSDs get removed
from the set?
On Tue, Jan 22, 2019 at 2:44 PM Wido den Hollander wrote:
> Hi,
>
> I've got a couple of PGs which are stuck in backfill_toofull,
Hi,
I've got a couple of PGs which are stuck in backfill_toofull, but none
of them are actually full.
"up": [
999,
1900,
145
],
"acting": [
701,
1146,
1880
],
"backfill_targets": [
"145",
"999",
"1900"
],
"acting_recovery_backfill": [
"145",
