CEPH filesystem development
 help / color / mirror / Atom feed
From: Greg Farnum <gregory.farnum@dreamhost.com>
To: Samuel Just <sam.just@dreamhost.com>,
	Damien Churchill <damoxc@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: pgs stuck inactive
Date: Tue, 10 Apr 2012 16:40:21 -0700	[thread overview]
Message-ID: <3154FE08568349E9B9EB0EBBCE4EDFB2@dreamhost.com> (raw)
In-Reply-To: <CACLRD_11ahz6h1yKhC7CVAxM8ha-BkOVztb3zBkhyo4Kd4t6aQ@mail.gmail.com>

On Tuesday, April 10, 2012 at 4:00 PM, Samuel Just wrote:
> Can you send along the osd log as well for comparison?
> -Sam
> 
> On Tue, Apr 10, 2012 at 3:03 PM, Damien Churchill <damoxc@gmail.com (mailto:damoxc@gmail.com)> wrote:
> > Here are the monitor logs, they're from the monitor starts, however I
> > restarted the osd shortly afterwards and left it to run for 5 or so
> > minutes.
> > 
> > http://damoxc.net/ceph/mon.node21.log.gz
> > http://damoxc.net/ceph/mon.node22.log.gz
> > http://damoxc.net/ceph/mon.node23.log.gz
> > 
> > On 10 April 2012 22:49, Samuel Just <sam.just@dreamhost.com (mailto:sam.just@dreamhost.com)> wrote:
> > > Nothing apparent from the backtrace. I need monitor logs from when
> > > the osd is sending pg_temp requests. Can you restart the osd and post
> > > the osd and all three monitor logs from when you restarted the osd?
> > > You'll have to enable monitor logging on all three.
> > > -Sam
> > 
> 


A quick glance through these shows that all the pg_temp requests aren't actually requesting any changes from the monitor. It's either a very serious mon bug which happened a while ago (unlikely, given the restarts and ongoing map changes, etc), or an OSD bug. I think we want logs from both osd.0 and osd.3 at the same time, from what I'm seeing. :)
-Greg


  reply	other threads:[~2012-04-10 23:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  8:12 pgs stuck inactive Damien Churchill
2012-04-04 20:51 ` Samuel Just
2012-04-04 21:44   ` Damien Churchill
2012-04-06 16:50     ` Samuel Just
2012-04-06 16:55       ` Damien Churchill
2012-04-06 17:30         ` Samuel Just
2012-04-06 17:53           ` Damien Churchill
     [not found]             ` <CACLRD_3hqoOqbZWnyft3B+pEaPG=pmiDt5HeQASUC=OPS-uA7Q@mail.gmail.com>
     [not found]               ` <CAFtEh-dnR0zu=ct-gG0L+76BTYHVFimjFKNhHjnDNZWA=Scs1g@mail.gmail.com>
2012-04-06 18:20                 ` Samuel Just
     [not found]                   ` <CAFtEh-cx2by6yG_xiQbq5e2fbViOWyHoaOLFPBCZgX7x-7gwFA@mail.gmail.com>
     [not found]                     ` <CACLRD_0UrwKJuELiZqrL7Q_5AjB1EvOd5gqLRzrxw_7AFMcjxg@mail.gmail.com>
     [not found]                       ` <CAFtEh-fwt9BwZ7NwZaJVnwq3hgzvkrb1XvKT0uF81vePRcu7oA@mail.gmail.com>
2012-04-10 21:49                         ` Samuel Just
2012-04-10 22:03                           ` Damien Churchill
2012-04-10 23:00                             ` Samuel Just
2012-04-10 23:40                               ` Greg Farnum [this message]
2012-04-12 15:29                                 ` Damien Churchill
2012-04-13 19:30                                   ` Greg Farnum
2012-04-13 19:42                                     ` Damien Churchill
2012-04-17  0:06                                       ` Greg Farnum
2012-04-17  5:32                                         ` Damien Churchill
2012-04-17 16:49                                           ` Greg Farnum
2012-04-18  4:35                                             ` Martin Wilderoth
2012-04-18  6:41                                             ` Damien Churchill
2012-04-18 18:41                                               ` Greg Farnum
2012-04-18 19:04                                                 ` Damien Churchill
2012-04-18 20:41                                                   ` Greg Farnum
2012-04-19  9:07                                                     ` Damien Churchill
2012-04-19 17:09                                                       ` Greg Farnum

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=3154FE08568349E9B9EB0EBBCE4EDFB2@dreamhost.com \
    --to=gregory.farnum@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=damoxc@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox