From: Josh Durgin <josh.durgin@inktank.com>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Pg stuck stale...why?
Date: Tue, 10 Jul 2012 18:22:07 -0700 [thread overview]
Message-ID: <4FFCD53F.108@inktank.com> (raw)
In-Reply-To: <4FFCD2AC.3040809@catalyst.net.nz>
On 07/10/2012 06:11 PM, Mark Kirkwood wrote:
> I am seeing this:
>
> # ceph -s
> health HEALTH_WARN 256 pgs stale; 256 pgs stuck stale
> monmap e1: 3 mons at
> {ved1=192.168.122.11:6789/0,ved2=192.168.122.12:6789/0,ved3=192.168.122.13:6789/0},
> election epoch 18, quorum 0,1,2 ved1,ved2,ved3
> osdmap e62: 4 osds: 4 up, 4 in
> pgmap v47148: 768 pgs: 512 active+clean, 256 stale+active+clean; 2224 MB
> data, 15442 MB used, 86907 MB / 102350 MB avail
> mdsmap e1: 0/0/1
>
> In particular 256 pgs stuck stale - I've tried a) waiting a while
> (overnight), b) a rolling restart of all 4 osd's, c) restarting all ceph
> services on all 4 nodes. All without changing this.
>
> As far as I understand what stuck state means, I can't see why they need
> to stay that way, given all osd's and mon's are up. (I have no mds
> configured)....any ideas? Or is this just expected?
>
> Regards
>
> Mark
What does 'ceph pg dump_stuck stale' show? Stale means that the
monitors haven't gotten updates about those pgs from the osds within
the a certain period of time (default is 300 seconds), so something may
be wrong with your crushmap or those pgs themselves.
Josh
next prev parent reply other threads:[~2012-07-11 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 1:11 Pg stuck stale...why? Mark Kirkwood
2012-07-11 1:22 ` Josh Durgin [this message]
2012-07-11 1:32 ` Mark Kirkwood
2012-07-11 1:35 ` Mark Kirkwood
2012-07-11 1:55 ` Josh Durgin
2012-07-11 2:09 ` Mark Kirkwood
2012-07-11 3:23 ` Mark Kirkwood
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=4FFCD53F.108@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mark.kirkwood@catalyst.net.nz \
/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.