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@xxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
