Your client needs to tell the cluster that the objects have been deleted. '-o discard' is my goto because I'm lazy and it works well enough for me. If you're in need of more performance, then fstrim is the other option. Nothing on the Ceph side can be configured to know when a client no longer needs the contents of an object. It just acts like a normal harddrive in that the filesystem on top of the RBD removed the pointers to the objects, but the disk just lets the file stay where it is until it is eventually overwritten.
Utilizing discard or fstrim cleans up the objects immediately, but at the cost of cluster iops. If you know that a particular RBD overwrites its data all the time, then you can skip using fstrim on it as it will constantly be using the same objects anyway.
On Fri, Oct 27, 2017 at 1:17 PM nigel davies <nigdav007@xxxxxxxxx> wrote:
_______________________________________________Hay allI am new to ceph and made an test ceph cluster that supportss3 and rbd's (rbd's are linked using iscsi)I been looking about and notice that the space is not decreasing when i delete a file and in turn filled up my cluster osd'sI have been doing some reading and see people recomandadding "-o discard" to every RBD mount (what can be an performance hit) or use fstrim. When i try both options work, but is their an better/another option.Thanks
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
