From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Paxos and long-lasting deleted data
Date: Thu, 31 Jan 2013 18:41:19 +0000 [thread overview]
Message-ID: <510ABACF.7040703@inktank.com> (raw)
In-Reply-To: <CABYiri8fbbpuhh0RguqdsmYEbEkYz_+PKO4UJqWqKb1TwDcc6A@mail.gmail.com>
On 01/31/2013 06:17 PM, Andrey Korolyov wrote:
> Hi,
>
> Please take a look, this data remains for days and seems not to be
> deleted in future too:
>
> pool name category KB objects clones
> degraded unfound rd rd KB wr
> wr KB
> data - 0 0 0
> 0 0 0 0 0
> 0
> install - 15736833 3856 0
> 0 0 16 3 464648
> 60970390
> metadata - 0 0 0
> 0 0 0 0 0
> 0
> prod-rack0 - 364027905 88895 0
> 0 0 32 0 267626
> 689034186
> rbd - 4194305 1027 0
> 0 0 4 1 11269
> 25165828
> total used 6900914368 93778
> total avail 18335469376
> total space 25236383744
>
> for pool in $(rados lspools) ; do rbd ls -l $pool ; done | grep -v
> SIZE | awk '{ sum += $2} END { print sum }'
> rbd: pool data doesn't contain rbd images
> rbd: pool metadata doesn't contain rbd images
> 526360
>
> I have same thing before, but not so contrast as there. Cluster was
> put on moderate failure test, dropping one or two osds at once under
> I/O pressure with replication factor three.
Just wondering if there was something else you wanted to discuss on your
email given the email subject. Wanted by any chance discuss anything
regarding Paxos?
-Joao
prev parent reply other threads:[~2013-01-31 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 18:17 Paxos and long-lasting deleted data Andrey Korolyov
2013-01-31 18:31 ` Gregory Farnum
2013-01-31 18:50 ` Andrey Korolyov
2013-01-31 18:56 ` Gregory Farnum
2013-01-31 19:18 ` Andrey Korolyov
2013-02-03 19:45 ` Andrey Korolyov
2013-02-03 21:46 ` Gregory Farnum
2013-02-04 5:31 ` Andrey Korolyov
2013-02-04 8:46 ` Chen, Xiaoxi
2013-01-31 18:41 ` Joao Eduardo Luis [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=510ABACF.7040703@inktank.com \
--to=joao.luis@inktank.com \
--cc=andrey@xdel.ru \
--cc=ceph-devel@vger.kernel.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.