From: Alphe Salas <asalas@kepler.cl>
To: Christoph Hellwig <hch@infradead.org>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Forever growing data in ceph using RBD image
Date: Thu, 17 Jul 2014 14:17:50 -0400 [thread overview]
Message-ID: <53C8134E.8030802@kepler.cl> (raw)
In-Reply-To: <20140717164712.GA4690@infradead.org>
Alphe Salas
I.T ingeneer
On 07/17/2014 12:47 PM, Christoph Hellwig wrote:
> On Thu, Jul 17, 2014 at 10:11:09AM -0400, Alphe Salas wrote:
>> Usually when I talk to dev team about this problem they tell me that the
>> real problem is the lack of trim in XFS, but my own analysis shows that the
>> real problem is ceph internal way to handle data. It is ceph that never
>> discard any replicas and never "clean" itself to only keep records of the
>> data in use.
>
> XFS supports TRIM just fine - with -o discard it will issue TRIMs on
> unlink, and with fstrim you can do it explicitly. Note that the online
> discard might be very slow for all Linux filesystems, although I've not
> actually tested it on top of RBD.
>
I will test it again probably the point I missed it that you have to
unmount / remount the XFS RBD image in order to see the data disapear
from the real disk space old in ceph. I will try it today and comeback
with copy /paste of ceph -s etc..
> --
> 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:[~2014-07-17 18:17 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
2014-07-17 16:47 ` Christoph Hellwig
2014-07-17 18:17 ` Alphe Salas [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=53C8134E.8030802@kepler.cl \
--to=asalas@kepler.cl \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.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.