From: Mykola Golub <mgolub@mirantis.com>
To: Boris Lukashev <blukashev@sempervictus.com>
Cc: ceph-devel@vger.kernel.org, Sage Weil <sage@newdream.net>
Subject: Re: 7915 is not resolved
Date: Tue, 12 Jan 2016 08:53:06 +0200 [thread overview]
Message-ID: <20160112065305.GA16215@gmail.com> (raw)
In-Reply-To: <CAFUG7CcudK5zu0eezuTmZrsakE4s-oHyPss3cubSRL5txQmA9Q@mail.gmail.com>
On Mon, Jan 11, 2016 at 09:00:18PM -0500, Boris Lukashev wrote:
> In case anyone is following the mailing list later on, we spoke in IRC
> and Sage provided a patch - http://fpaste.org/309609/52550203/
> diff --git a/src/osd/PG.cc b/src/osd/PG.cc
> index dc18aec..f9ee23c 100644
> --- a/src/osd/PG.cc
> +++ b/src/osd/PG.cc
> @@ -135,8 +135,16 @@ void PGPool::update(OSDMapRef map)
> name = map->get_pool_name(id);
> if (pi->get_snap_epoch() == map->get_epoch()) {
> pi->build_removed_snaps(newly_removed_snaps);
> - newly_removed_snaps.subtract(cached_removed_snaps);
> - cached_removed_snaps.union_of(newly_removed_snaps);
> + interval_set<snapid_t> intersection;
> + intersection.intersection_of(newly_removed_snaps, cached_removed_snaps);
> + if (!(intersection == cached_removed_snaps)) {
> + newly_removed_snaps.subtract(cached_removed_snaps);
Sage, won't it still violate the assert?
"intersection != cached_removed_snaps" means that cached_removed_snaps
contains snapshots missed in newly_removed_snaps, and we can't subtract?
> + cached_removed_snaps.union_of(newly_removed_snaps);
> + } else {
> + lgeneric_subdout(g_ceph_context, osd, 0) << __func__ << " cached_removed_snaps shrank from " << cached_removed_snaps << dendl;
> + cached_removed_snaps = newly_removed_snaps;
> + newly_removed_snaps.clear();
> + }
> snapc = pi->get_snap_context();
> } else {
> newly_removed_snaps.clear();
--
Mykola Golub
next prev parent reply other threads:[~2016-01-12 6:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 16:52 7915 is not resolved Boris Lukashev
2016-01-11 17:25 ` Sage Weil
2016-01-11 18:15 ` Boris Lukashev
2016-01-11 19:06 ` Dmitry Borodaenko
2016-01-11 20:13 ` Boris Lukashev
2016-01-12 2:00 ` Boris Lukashev
2016-01-12 6:53 ` Mykola Golub [this message]
2016-01-12 13:24 ` Sage Weil
2016-01-12 17:43 ` Boris Lukashev
2016-01-12 17:47 ` Sage Weil
2016-01-12 18:03 ` Boris Lukashev
2016-01-12 20:21 ` Boris Lukashev
2016-01-13 1:06 ` Boris Lukashev
2016-01-13 11:35 ` Mykola Golub
2016-01-13 16:49 ` Alexey Sheplyakov
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=20160112065305.GA16215@gmail.com \
--to=mgolub@mirantis.com \
--cc=blukashev@sempervictus.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.