All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Samuel Just <sam.just@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Random blocks when accessing rbd images
Date: Thu, 15 Dec 2011 17:33:56 +0100	[thread overview]
Message-ID: <4EEA2174.2060002@widodh.nl> (raw)
In-Reply-To: <CACLRD_1LPhCC3szKfsj_pZ6-5rr=pr+P8KyWO76CxU6x0K17mA@mail.gmail.com>

On 12/15/2011 05:30 PM, Samuel Just wrote:
> 'ceph pg dump' will tell you the status (active/clean/scrubbing/etc)
> for each pg.  Does the same pg remain in state active+clean+scrubbing
> for more than 10 minutes?

Yes, from what I've seen it will block indefinitely until you restart 
one of the OSDs who are member of the PG.

Wido

> -Sam
>
> On Thu, Dec 15, 2011 at 7:45 AM, Guido Winkelmann
> <guido-ceph@thisisnotatest.de>  wrote:
>> Am Donnerstag, 15. Dezember 2011, 17:32:25 schrieben Sie:
>>> On 12/15/2011 05:07 PM, Guido Winkelmann wrote:
>>>> Hi,
>>>>
>>>> I've got a small ceph cluster with one mon, one mds and two osds (all on
>>>> the same machine, for now), that I want to use as a block- and file
>>>> storage backend for qemu machine virtualisation.
>>>>
>>>> I found that read access to some of the rbd images, or parts of some of
>>>> them sometimes blocks indefinitely, usually after the image has been
>>>> sitting around untouched for a while, for example over night. This has
>>>> the effect that virtual machines that try to access their disks as well
>>>> as rbd commands like "rbd cp" will just hang indefinitely.
>>>>
>>>>   I found that these blocks can usually be "fixed" by restarting one of
>>>>   the>
>>>> osds.
>>>>
>>>> The last time this happened, ceph -s reported one of the osds to be in
>>>> state "active+clean+scrubbing". (I'm afraid I don't have the complete
>>>> output from ceph -s anymore.)
>>>>
>>>> Does anybody have any idea what could be going wrong here?
>>>
>>> I think it's fixed in v0.39
>>
>> I'm already using 0.39, so, no. (Should have mentioned that to start with...)
>>
>>         Guido
>> --
>> 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


  reply	other threads:[~2011-12-15 16:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 15:07 Random blocks when accessing rbd images Guido Winkelmann
2011-12-15 15:13 ` Wido den Hollander
2011-12-15 15:32 ` Stratos Psomadakis
2011-12-15 15:45   ` Guido Winkelmann
2011-12-15 16:30     ` Samuel Just
2011-12-15 16:33       ` Wido den Hollander [this message]
2011-12-15 16:38         ` Martin Mailand
2011-12-15 16:44           ` Martin Mailand
2011-12-16 16:17             ` Wido den Hollander
2011-12-16 21:17               ` Samuel Just
2011-12-18 14:26                 ` Wido den Hollander
2011-12-22 13:59                 ` Martin Mailand
2011-12-15 16:45           ` Wido den Hollander
2011-12-15 16:44       ` Guido Winkelmann
2011-12-15 17:24         ` Stratos Psomadakis
2011-12-15 21:28           ` Samuel Just
2011-12-15 16:31     ` Martin Mailand
2011-12-15 16:51       ` Guido Winkelmann
2011-12-15 17:32       ` Guido Winkelmann

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=4EEA2174.2060002@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sam.just@dreamhost.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 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.