From: Alphe Salas <asalas@kepler.cl>
To: Sage Weil <sweil@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Forever growing data in ceph using RBD image
Date: Wed, 06 Aug 2014 15:02:11 -0400 [thread overview]
Message-ID: <53E27BB3.5030601@kepler.cl> (raw)
In-Reply-To: <53C83F22.4010502@kepler.cl>
How can I follow the state of advancement of the resolution of this
issue ? I really need it and I really need to know when it will be
release in order to immediatly install the new ceph version which patch
the forever growing data in ceph using RBD bold image (no QEMU etc..)
Alphe Salas
I.T ingeneer
On 07/17/2014 05:24 PM, Alphe Salas wrote:
> Thank you I though I was seeing things :)
> So it will come soon can I help chasing the things that give errors ?
>
>
>
> Alphe Salas
> I.T ingeneer
>
> On 07/17/2014 03:28 PM, Sage Weil wrote:
>> On Thu, 17 Jul 2014, Alphe Salas wrote:
>>> I don t use QEMU /KVM just a plain regular rbd image format 1 map and
>>> mounted
>>> to a real machine that is used as proxy for data droping to ceph.
>>
>> Oh, that explains part of it at least. The discard support isn't yet
>> upstream for the kernel RBD driver. The patches are mostly ready but
>> there was a QA failure they're chasing down first. Hopefully it will
>> make
>> it into the next kernel cycle.
>>
>> sage
>>
next prev parent reply other threads:[~2014-08-06 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 14:11 Forever growing data in ceph using RBD image Alphe Salas
2014-07-17 16:35 ` Sage Weil
2014-07-17 18:13 ` Alphe Salas
2014-07-17 18:27 ` Sage Weil
2014-07-17 18:53 ` Alphe Salas
2014-07-17 18:57 ` Christoph Hellwig
2014-07-17 19:19 ` Alphe Salas
2014-07-17 19:28 ` Sage Weil
2014-07-17 21:24 ` Alphe Salas
2014-08-06 19:02 ` Alphe Salas [this message]
2014-07-17 16:47 ` Christoph Hellwig
2014-07-17 18:17 ` Alphe Salas
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=53E27BB3.5030601@kepler.cl \
--to=asalas@kepler.cl \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
--cc=sweil@redhat.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.