From: flisky <yinjifeng@lianjia.com>
To: ceph-devel@vger.kernel.org
Subject: Re: [EMG]incomplete pgs make RGW unusable
Date: Tue, 19 May 2015 23:30:59 +0800 [thread overview]
Message-ID: <mjfkvj$a4$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1505190741450.9510@cobra.newdream.net>
Thanks, sage!
On 2015年05月19日 22:42, Sage Weil wrote:
> On Tue, 19 May 2015, flisky wrote:
>> I follow the instruction from http://tracker.ceph.com/issues/10411#note-4, and
>> finally get force_create_pg work.
>>
>> Thanks, Brian Rak. It helps a lot.
>>
>> And, it would be great if the [feature](http://tracker.ceph.com/issues/10098)
>> is implemented.
>
> I've bumped this up toward the top of the backlog.. it shouldn't be
> terribly difficult to implement!
>
> sage
>
>
>>
>> BR,
>>
>> On 2015?05?19? 08:06, flisky wrote:
>>> Hi core developers,
>>>
>>> Sorry, I have to raise this from user list because there is no response.
>>>
>>> I reformat the disks to increase osd journal size. During the process, I
>>> lost 9 pgs.
>>>
>>> The incomplete pgs belong to the pool .rgw.buckets, which causes slow
>>> requests and make RGW unusable.
>>> I have to restart the OSDs and RGWs time to time, to make RGW responsible.
>>>
>>> The most scary things happen. I cannot recovery the incomplete pgs.
>>>
>>> [force_create_pg](http://tracker.ceph.com/issues/10098) marks it a
>>> feature to handle this.
>>>
>>> The [blog](https://ceph.com/community/incomplete-pgs-oh-my/) is not
>>> working, either.
>>>
>>> And finally I give up the recovery, and use 'rados cppool' to copy our
>>> huge pool, it's STUCK...
>>>
>>> I'm very frustrated, and very surprised that Ceph doesn't offer a way to
>>> just let the lost data lost.
>>>
>>> Could anyone give any advise on this? Thanks!
>>>
>>> Sincerely,
>>>
>>> --
>>> 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
>>
>>
> --
> 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
prev parent reply other threads:[~2015-05-19 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 0:06 [EMG]incomplete pgs make RGW unusable flisky
2015-05-19 8:57 ` flisky
2015-05-19 14:42 ` Sage Weil
2015-05-19 15:30 ` flisky [this message]
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='mjfkvj$a4$1@ger.gmane.org' \
--to=yinjifeng@lianjia.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 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.