From: Qiang <wangqiang.hunan@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Iusse: Ceph osd rm one osd cause 30% objects degraded
Date: Wed, 19 Nov 2014 19:29:50 +0800 [thread overview]
Message-ID: <546C7F2E.8020207@gmail.com> (raw)
Hi, Dear ceph-devel
I met a issue: Ceph osd rm one osd cause 30% objects degraded.
Step 1:
#created a ssd root
ceph osd crush add-bucket ssd root
Step 2: Installed a osd.100 failed:
94 1 osd.94 up 1
95 1 osd.95 up 1
96 1 osd.96 up 1
97 1 osd.97 up 1
98 1 osd.98 up 1
99 1 osd.99 up 1
100 0 osd.100 down 0
Step 3: Installed a osd.101 again successfully. Move a host into root=ssd.
-12 1 root ssd
-13 1 host ssd-cephnode1
101 1 osd.101 up 1
-1 100 root default
-2 10 host cephnode1
0 1 osd.0 up 1
1 1 osd.1 up 1
2 1 osd.2 up 1
Step 4: Then I ceph osd rm 100, but the the ceph health turned into 30%
objects degraded. Then the io performance downgrade to very slow (1MB/s
each clients).
Anybody know what is the root cause? Or some suggestions to finger it out?
Thank you very much.
next reply other threads:[~2014-11-19 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 11:29 Qiang [this message]
2014-11-19 15:30 ` Issue: Ceph osd rm one osd cause 30% objects degraded Qiang
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=546C7F2E.8020207@gmail.com \
--to=wangqiang.hunan@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox