From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Wido den Hollander <wido@widodh.nl>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: KVM/RBD Block device hangs
Date: Mon, 21 May 2012 16:50:47 +0200 [thread overview]
Message-ID: <4FBA5647.40101@profihost.ag> (raw)
In-Reply-To: <4FBA559D.7040902@widodh.nl>
Am 21.05.2012 16:47, schrieb Wido den Hollander:
> What do you mean the OSD crashes? I assume you have multiple OSD's in
> your cluster and one of them crashes? Or do ALL of them do go down?
2 of them went down (1st then 10 minutes later the 2nd)
>> What's next / wrong?
>
> Could you fetch the last 100 line from the log file and also tell us
> which version you are running?
i'm upgrading right now to v0.47 and will try to reproduce.
> Also, the output of "ceph -s" might be useful.
before or after the crash?
Stefan
next prev parent reply other threads:[~2012-05-21 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:44 KVM/RBD Block device hangs Stefan Priebe - Profihost AG
2012-05-21 14:47 ` Wido den Hollander
2012-05-21 14:50 ` Stefan Priebe - Profihost AG [this message]
2012-05-21 14:59 ` Wido den Hollander
2012-05-21 20:51 ` Stefan Priebe
2012-05-21 20:57 ` Gregory Farnum
2012-05-22 12:47 ` Stefan Priebe - Profihost AG
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=4FBA5647.40101@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@widodh.nl \
/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.