All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: Chris Dunlop <chris@onthe.net.au>
Cc: ceph-devel@vger.kernel.org
Subject: Re: cmon: PGMonitor::encode_pending() assert failure
Date: Thu, 3 Feb 2011 14:24:43 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1102031424000.19855@cobra.newdream.net> (raw)
In-Reply-To: <20110203220245.GA6179@onthe.net.au>

On Fri, 4 Feb 2011, Chris Dunlop wrote:
> On Thu, Feb 03, 2011 at 01:03:17PM -0800, Sage Weil wrote:
> > Hi Chris,
> > 
> > This is an interesting one.  Would it be possible for you to
> > tar up your mondata directory on the failed node and post it
> > somewhere I can get at it?  From the looks of things the pgmap
> > incremental state file is truncated, but I'd like to confirm.
> > 
> > http://tracker.newdream.net/issues/762
> 
> Aw crap, sorry, I blew that fs away installing the latest master
> to see what happened there ...whereupon overnight I've promptly
> hit the "WARNING: at fs/btrfs/inode.c:2143" problem*.
> 
> I can revert back to my previous install and run the same
> workload to see if it crops up again if that's useful (it took
> about 12 hours of rsync'ing files into the fs to get there), or
> I can try the workload using latest ceph with Josef Bacik's
> btrfs-work** to see if either problem crops up again. Any
> preference?

Let's go with latest master and latest bits from Josef.  It's the future!

Thanks!
sage


  reply	other threads:[~2011-02-03 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03  1:51 cmon: PGMonitor::encode_pending() assert failure Chris Dunlop
     [not found] ` <AANLkTi=SyqVD8MyCt+ybYrhoSHunYrchcdZUvW-nzOgw@mail.gmail.com>
2011-02-03 21:03   ` Sage Weil
2011-02-03 22:02     ` Chris Dunlop
2011-02-03 22:24       ` Sage Weil [this message]
2011-02-03 23:24         ` Chris Dunlop
2011-02-07  3:34         ` Chris Dunlop

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=Pine.LNX.4.64.1102031424000.19855@cobra.newdream.net \
    --to=sage@newdream.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chris@onthe.net.au \
    /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.