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: Fri, 03 Oct 2014 07:09:41 +1000 [thread overview]
Message-ID: <4085610.Ynnm5zoT22@debstor> (raw)
In-Reply-To: <alpine.DEB.2.00.1410020824060.14393@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On Thu, 2 Oct 2014 08:28:16 Sage Weil wrote:
> My guess is a btrfs issue. The weird thing about your report is the byte
> totals are off by an uneven number of bytes (3 bytes, 9 bytes, etc.).
> We haven't ever seen this. We do test RBD over cache tiers on btrfs,
> but not with EC on the base. I'll add that combo to the matrix. My first
> guess is a btrfs issue, honestly.
I think I found where it is happening: for a while I was using Btrfs-based
OSDs with journals on ext4 partition on SSD. As an experiment I've decided to
try moving all journal files back to their OSDs and it eliminated
inconsistencies. I've updated the ticket with this information.
This behaviour is reproducible on 0.80.6.
It looks like Btrfs snapshotting do not affect this issue.
> Does it continue to come up after the kernels are upgraded (and after a
> full cycle of scrub and repairs have been done to clear out
> inconsistencies introduced while running the older kernel)?
Yes, I tried many times after every kernel update or any change in cluster
whatsoever. Repair is usually ineffective and doesn't change anything: it
would log "repair 1 errors, 1 fixed" but "ceph pg scrub" will find an error
right away. Moreover repair is not even necessary -- inconsistencies stay on
some PGs for a while then "move" to different PGs. For example "ceph pg scrub
19.NN" sometimes would be clearing affected pg from "inconsistent" state or
discover a new inconsistency seemingly at random.
Thank you.
--
Cheers,
Dmitry Smirnov.
---
Odious ideas are not entitled to hide from criticism behind the human
shield of their believers' feelings.
-- Richard Stallman
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-10-02 21:09 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 ` issue #8752 (inconsistent PGs on RBD caching pool) Dmitry Smirnov
2014-10-02 15:28 ` Sage Weil
2014-10-02 21:09 ` Dmitry Smirnov [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=4085610.Ynnm5zoT22@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.