From: Andrey Korolyov <andrey@xdel.ru>
To: ceph-devel@vger.kernel.org
Subject: ceph status reporting non-existing osd
Date: Fri, 13 Jul 2012 12:17:47 +0400 [thread overview]
Message-ID: <4FFFD9AB.40608@xdel.ru> (raw)
Hi,
Recently I`ve reduced my test suite from 6 to 4 osds at ~60% usage on
six-node,
and I have removed a bunch of rbd objects during recovery to avoid
overfill.
Right now I`m constantly receiving a warn about nearfull state on
non-existing osd:
health HEALTH_WARN 1 near full osd(s)
monmap e3: 3 mons at
{0=192.168.10.129:6789/0,1=192.168.10.128:6789/0,2=192.168.10.127:6789/0},
election epoch 240, quorum 0,1,2 0,1,2
osdmap e2098: 4 osds: 4 up, 4 in
pgmap v518696: 464 pgs: 464 active+clean; 61070 MB data, 181 GB
used, 143 GB / 324 GB avail
mdsmap e181: 1/1/1 up {0=a=up:active}
HEALTH_WARN 1 near full osd(s)
osd.4 is near full at 89%
Needless to say, osd.4 remains only in ceph.conf, but not at crushmap.
Reducing has been done 'on-line', e.g. without restart entire cluster.
next reply other threads:[~2012-07-13 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 8:17 Andrey Korolyov [this message]
2012-07-13 17:03 ` ceph status reporting non-existing osd Gregory Farnum
2012-07-13 17:09 ` Sage Weil
2012-07-14 14:20 ` Andrey Korolyov
2012-07-16 16:12 ` Gregory Farnum
2012-07-16 18:42 ` Andrey Korolyov
2012-07-16 18:48 ` Gregory Farnum
2012-07-16 18:55 ` Andrey Korolyov
2012-07-18 6:09 ` Gregory Farnum
2012-07-18 6:22 ` Andrey Korolyov
2012-07-18 7:18 ` Gregory Farnum
2012-07-18 7:47 ` Andrey Korolyov
2012-07-18 18:30 ` Gregory Farnum
2012-07-18 19:07 ` Andrey Korolyov
2012-07-18 21:28 ` Gregory Farnum
2012-07-19 6:17 ` Andrey Korolyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFFD9AB.40608@xdel.ru \
--to=andrey@xdel.ru \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.