From: Dmitry Smirnov <onlyjob@debian.org>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: issue #8752 (inconsistent PGs on RBD caching pool)
Date: Thu, 02 Oct 2014 23:47:13 +1000 [thread overview]
Message-ID: <3415192.gCaj5vu5sy@debstor> (raw)
In-Reply-To: <alpine.DEB.2.00.1409211900410.27396@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Sun, 21 Sep 2014 19:01:52 Sage Weil wrote:
> This is one we have never seen in our QA environment, and no real leads.
I'm much surprised about this... Is it really that unusual to use replicated
caching pool in front of RBD erasure pool? All my OSDs are Btrfs-based and
recently I've upgraded all kernels (i.e. kernel RBD clients) to 3.16.3.
Unlike some shifty issues that may be hard to replicate this particular one
was very persistent and noticeable, no effort to reproduce at all. I've been
observing it for several months already...
It is unlikely that I have anything special in my v0.80.5 cluster's
configuration...
> There are a couple slightly different scrub issues that pop up
> occasionally that we are trying to nail down, but this one is a bit
> different. Being able to reliably reproduce it and generate logs is the
> usual strategy...
Please advise what kind of logs could be useful. Something like "(debug ms =
1, debug osd = 20)" from primary OSD where inconsistent PG lies at a time when
"scrub" command is given?
Thanks.
--
All the best,
Dmitry Smirnov.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-10-02 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 23:43 issue 8747 / 9011 Sage Weil
2014-09-20 3:08 ` Dmitry Smirnov
2014-09-21 19:28 ` Sage Weil
2014-09-22 1:13 ` Dmitry Smirnov
2014-09-22 2:01 ` Sage Weil
2014-10-02 13:47 ` Dmitry Smirnov [this message]
2014-10-02 15:28 ` issue #8752 (inconsistent PGs on RBD caching pool) Sage Weil
2014-10-02 21:09 ` Dmitry Smirnov
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=3415192.gCaj5vu5sy@debstor \
--to=onlyjob@debian.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.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.