All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Cc: Sage Weil <sage@inktank.com>
Subject: Re: inconsistent snapcolls
Date: Tue, 19 Mar 2013 15:14:56 +0100	[thread overview]
Message-ID: <514872E0.3070708@profihost.ag> (raw)
In-Reply-To: <514821B0.3090706@profihost.ag>

Hi Sage,

could it be that this one needs to be backported to bobtail?

http://tracker.ceph.com/issues/4071

Is this hte error i'm seeing? I can't find that commit in the bobtail
branch.
Am 19.03.2013 09:28, schrieb Stefan Priebe - Profihost AG:
> Hello,
> 
> for testing purposes i've upgrade bobtail 0.56.3 to latest bobtail branch.
> 
> Since then i'm seeing a lot of messages like these:
> 
> 2013-03-19 09:27:06.089820 osd.32 [ERR] 4.ac6 osd.41 inconsistent
> snapcolls on 34762ac6/rbd_data.26c8856b8b4567.0000000000000025/df3//4
> found be1 expected be1,df1
> 
> What do they mean?
> Does ceph fix them automatically?

Stefan

      reply	other threads:[~2013-03-19 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19  8:28 inconsistent snapcolls Stefan Priebe - Profihost AG
2013-03-19 14:14 ` Stefan Priebe - Profihost AG [this message]

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=514872E0.3070708@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.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 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.