All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva-mXXj517/zsQ@public.gmane.org>
To: Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: v0.75 released
Date: Sat, 18 Jan 2014 04:50:57 -0200	[thread overview]
Message-ID: <ord2jpvl4e.fsf@livre.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1401141941070.8325-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org> (Sage Weil's message of "Tue, 14 Jan 2014 19:42:31 -0800 (PST)")

On Jan 15, 2014, Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org> wrote:

>  v0.75 291 files changed, 82713 insertions(+), 33495 deletions(-)

> Upgrading
> ~~~~~~~~~

I suggest adding:

  * All (replicated?) pools will likely fail scrubbing because the
    per-pool dirty object counts, introduced in 0.75, won't match.  This
    inconsistency is cleared by a pg repair; unfortunately this is about
    as expensive as a a deep-scrub, and it's not automatically scheduled
    or retried, like scrubs and deep-scrubs.

I suppose after the dirty counts are brought to sync, the next scrub
won't find inconsistent counts again, but I haven't got to that point
yet.

What surprised me was the huge number of objects marked as dirty!  It
was at least 14k out of 70k objects in each data pool, and even more in
metadata pools, but it's not like I have messed with this many objects
recently.  Could something be amiss there?

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist     Red Hat Brazil Toolchain Engineer

  parent reply	other threads:[~2014-01-18  6:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  3:42 v0.75 released Sage Weil
2014-01-16 13:51 ` Ilya Dryomov
     [not found]   ` <CALFYKtAz5G4y1RUoqJmyr5psuh1NvD=E_7qSPm7WL+8Ra_bJ5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-17  0:05     ` Christian Balzer
     [not found]       ` <20140117090518.3f988b32-9yhXNL7Kh0lSCLKNlHTxZM8NsWr+9BEh@public.gmane.org>
2014-01-17  9:20         ` Ilya Dryomov
     [not found]           ` <CALFYKtBizOcjv9i5EkW7HLBdsNUzBCZ1oO1ZTaDWh8cwgK-tww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-17 10:02             ` Ilya Dryomov
     [not found] ` <alpine.DEB.2.00.1401141941070.8325-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-01-18  6:50   ` Alexandre Oliva [this message]
     [not found]     ` <ord2jpvl4e.fsf-o1YuAO9g/txBDLzU/O5InQ@public.gmane.org>
2014-01-18  6:58       ` Mark Kirkwood
2014-01-19  5:00       ` Sage Weil
2014-01-19  5:27         ` Sage Weil
     [not found]           ` <alpine.DEB.2.00.1401182125150.17005-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-01-21 15:33             ` Alexandre Oliva

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=ord2jpvl4e.fsf@livre.home \
    --to=oliva-mxxj517/zsq@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org \
    /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.