From: David McBride <dwm37@cam.ac.uk>
To: Roald van Loon <roaldvanloon@gmail.com>
Cc: Ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Negative degradation?
Date: Tue, 30 Jul 2013 14:07:12 +0100 [thread overview]
Message-ID: <51F7BA80.4040800@cam.ac.uk> (raw)
In-Reply-To: <CAN04cT7aidUFqHLPhQcT6s-A51KMQxY8hVNoOBYT9aobxTmjAw@mail.gmail.com>
On 30/07/13 09:20, Roald van Loon wrote:
> Came across it this morning when booting my development environment,
> has anyone seen this before?
>
> It's with 0.67-rc2;
>
> 2013-07-30 08:09:09.230349 mon.0 [INF] pgmap v4172: 1216 pgs: 123
> active, 219 active+clean, 161 active+clean+replay, 713 peering; 241 MB
> data, 630 MB used, 5483 MB / 6114 MB avail; -2/588 degraded (-0.340%)
I saw similar negative values when updating my test OSD host to 0.67-rc2
from 0.66 this morning; however, I've seen such negative values being
reported at various times over a number of past releases.
I suspect there's a defect in signed-ness handling somewhere, or similar
— however, it appears to be cosmetic and disappears when the OSD replay
completes.
(I've likewise seen impossible values for other statistics being
reported — a while back I saw multiple EBs being reported as being
read/written during a resync between 4 disks, for example. I suspect
this is another manifestation of a similar problem.)
Cheers,
David
--
David McBride <dwm37@cam.ac.uk>
Unix Specialist, University Computing Service
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-30 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 8:20 Negative degradation? Roald van Loon
2013-07-30 13:07 ` David McBride [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=51F7BA80.4040800@cam.ac.uk \
--to=dwm37@cam.ac.uk \
--cc=ceph-devel@vger.kernel.org \
--cc=roaldvanloon@gmail.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.