From: Mark Nelson <mark.nelson@inktank.com>
To: "Blinick, Stephen L" <stephen.l.blinick@intel.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Memstore issue on v0.91
Date: Wed, 21 Jan 2015 08:13:03 -0600 [thread overview]
Message-ID: <54BFB3EF.1030800@redhat.com> (raw)
In-Reply-To: <3649A15A2562B54294DE14BCE5AC79120AB3CD9F@FMSMSX106.amr.corp.intel.com>
On 01/21/2015 01:48 AM, Blinick, Stephen L wrote:
> Moved to 0.91 yesterday and ran into some issues, with a Memstore OSD of default size. After a few hundred K OPS client gets a FULL message and the avail space looks like:
>
> [root@cephtestnode0 bmpa]# rados df
> pool name KB objects clones degraded unfound rd rd KB wr wr KB
> rbd 0 0 0 0 0 0 0 0 0
> testmemstore 1505052 376263 0 0 0 0 0 376263 1505052
> total used 1494247 376263
> total avail 18014398508987737
> total space 1000000
>
> I was looking at pull request #2836 and found a case where there could be an unsigned int underflow in MemStore.cc:statfs:
>
> st->f_bfree = st->f_bavail = MAX((st->f_blocks - used_bytes / st->f_bsize), 0);
>
> But that wasn't the final issue.. I put some asserts where used_bytes could underflow as well and didn't catch anything. I will keep digging but wanted to find out if anyone else was seeing the issue as well.
FWIW, I hit this yesterday too. I hadn't started debugging it yet
though. Looks like you are farther along than I am, thanks Stephen! :)
>
> Thanks,
>
> Stephen
>
>
>
> --
> 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
>
next prev parent reply other threads:[~2015-01-21 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 7:48 Memstore issue on v0.91 Blinick, Stephen L
2015-01-21 14:13 ` Mark Nelson [this message]
2015-01-22 8:38 ` Chen, Xiaoxi
2015-01-22 23:25 ` Blinick, Stephen L
2015-01-23 0:41 ` 回复: " Chen, Xiaoxi
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=54BFB3EF.1030800@redhat.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mnelson@redhat.com \
--cc=stephen.l.blinick@intel.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.