From: Stefan Priebe <s.priebe@profihost.ag>
To: Samuel Just <sam.just@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: still recovery issues with cuttlefish
Date: Thu, 01 Aug 2013 20:46:36 +0200 [thread overview]
Message-ID: <51FAAD0C.5060400@profihost.ag> (raw)
In-Reply-To: <CA+4uBUY52Ft+6CC9RSq38ff7u=MA7TnFdKL4dSrTxnNBXXeEqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
here it is
Am 01.08.2013 20:36, schrieb Samuel Just:
> For now, just the main ceph.log.
> -Sam
>
> On Thu, Aug 1, 2013 at 11:34 AM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> m 01.08.2013 20:34, schrieb Samuel Just:
>>
>>> Can you reproduce and attach the ceph.log from before you stop the osd
>>> until after you have started the osd and it has recovered?
>>> -Sam
>>
>>
>> Sure which log levels?
>>
>>
>>> On Thu, Aug 1, 2013 at 1:22 AM, Stefan Priebe - Profihost AG
>>> <s.priebe@profihost.ag> wrote:
>>>>
>>>> Hi,
>>>>
>>>> i still have recovery issues with cuttlefish. After the OSD comes back
>>>> it seem to hang for around 2-4 minutes and then recovery seems to start
>>>> (pgs in recovery_wait start to decrement). This is with ceph 0.61.7. I
>>>> get a lot of slow request messages an hanging VMs.
>>>>
>>>> What i noticed today is that if i leave the OSD off as long as ceph
>>>> starts to backfill - the recovery and "re" backfilling wents absolutely
>>>> smooth without any issues and no slow request messages at all.
>>>>
>>>> Does anybody have an idea why?
>>>>
>>>> Greets,
>>>> Stefan
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
[-- Attachment #2: ceph.log.gz --]
[-- Type: application/gzip, Size: 40224 bytes --]
next prev parent reply other threads:[~2013-08-01 18:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 8:22 still recovery issues with cuttlefish Stefan Priebe - Profihost AG
2013-08-01 14:50 ` Andrey Korolyov
2013-08-01 18:38 ` Samuel Just
2013-08-02 17:56 ` Andrey Korolyov
2013-08-01 18:34 ` Samuel Just
2013-08-01 18:34 ` Stefan Priebe
2013-08-01 18:36 ` Samuel Just
2013-08-01 18:36 ` Samuel Just
2013-08-01 18:46 ` Stefan Priebe [this message]
2013-08-01 18:54 ` Mike Dawson
2013-08-01 19:07 ` Stefan Priebe
2013-08-01 21:23 ` Samuel Just
2013-08-02 7:44 ` Stefan Priebe
2013-08-02 17:35 ` Samuel Just
2013-08-02 18:16 ` Stefan Priebe
2013-08-02 18:21 ` Samuel Just
2013-08-02 18:46 ` Stefan Priebe
2013-08-08 14:05 ` Mike Dawson
2013-08-08 15:43 ` Oliver Francke
2013-08-08 18:13 ` Stefan Priebe
2013-08-09 21:44 ` Samuel Just
2013-08-10 19:08 ` Stefan Priebe
2013-08-11 3:50 ` Samuel Just
2013-08-13 4:39 ` Stefan Priebe - Profihost AG
2013-08-13 5:34 ` Samuel Just
2013-08-13 20:43 ` Samuel Just
2013-08-13 21:03 ` Stefan Priebe - Profihost AG
2013-08-13 23:11 ` Samuel Just
2013-08-14 7:04 ` Stefan Priebe - Profihost AG
2013-08-21 15:28 ` Mike Dawson
2013-08-21 15:32 ` Samuel Just
2013-08-21 16:25 ` Yann ROBIN
2013-08-21 17:12 ` Samuel Just
2013-08-21 17:55 ` Mike Dawson
2013-08-21 18:05 ` Samuel Just
2013-08-21 18:21 ` Stefan Priebe
2013-08-21 19:13 ` Samuel Just
2013-08-21 19:37 ` Stefan Priebe
2013-08-22 3:34 ` Samuel Just
2013-08-22 7:41 ` 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=51FAAD0C.5060400@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=sam.just@inktank.com \
/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