On Friday, April 13, 2012 at 12:42 PM, Damien Churchill wrote:
> Hi, > > On 13 April 2012 20:30, Greg Farnum <[email protected] > (mailto:[email protected])> wrote: > > On Thursday, April 12, 2012 at 8:29 AM, Damien Churchill wrote: > > > On 11 April 2012 00:40, Greg Farnum <[email protected] > > > (mailto:[email protected])> wrote: > > > > > > > > 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 > > > > > > > > > > > > > > > > > > Just to make sure all bases are covered: > > > > > > http://damoxc.net/ceph/ceph-logs-20120412142537.tar.gz > > > > > > This contains all 5 osd logs and all 3 monitor logs, everything > > > restarted with debug logging prior to capturing the logs. > > > > > > > > I (and Sam) spent some time looking at this very closely. It continues to > > tell me that the OSD and the monitor are disagreeing on whether osd 3 > > should be in the pg temp set for some things, but they seem to agree on > > everything else…. > > Can you zip up for me: > > 1) The files matching osdmap* of osd0's store from the current/meta/ > > directory, > > 2) The contents of your lead monitor's osdmap and osdmap_full directories? > > > > Here they are > > http://damoxc.net/ceph/osdmap.0.tar.gz > http://damoxc.net/ceph/mon.node21.osdmap.tar.gz > > Hopefully I got the right files :) Yep! We looked into this more today and have discovered some definite oddness. Have you by any chance tried to change the number of PGs in your pools? -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
