https://bugzilla.redhat.com/show_bug.cgi?id=1486862
--- Comment #4 from M. Scherer <msche...@redhat.com> --- I have improved/fixed the cleanup script ( https://github.com/gluster/gluster.org_ansible_configuration/commit/2355f453429012621855b5995667e214b79898c8 ). Now, it will automatically recompress files that were wrongfully compressed (due to disk being full, OOM errors, etc) and so the problem should fix itself now (instead of seeing the issue persist). I can still imagine some concurrency (like if the server do crash hard at the exact wrong moment and the wrong day), but we are not gonna get a better system without significant time spent on it. I did a manual cleanup a few files, and watched. I may need to later change the partition layout (since we are down at 30G of logs, with 30G of free space for partition ) but since that's xfs, it can't be done online. For what I see, the files are all here, so closing. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aaFtTeWajN&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
